https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24201
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Last reconfirmed|2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24201
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
--- Comment #6 from hjl at lucon dot org 2005-10-05 00:37 ---
I used libstdc++ as an example to show that it isn't unreasonable to have
.o files compiled with and without -fffunction-sections. Besides, on my system
there is a libstdc++.a. We can just use something like
#define HOT_TEXT_
--- Comment #5 from pinskia at gcc dot gnu dot org 2005-10-04 23:14 ---
(In reply to comment #4)
> A library may be compiled with -ffunction-sections. It doesn't mean that all
> codes linked against that library have to use -ffunction-sections. For
> example,
> libstdc++ is compiled wit
--- Comment #4 from hjl at lucon dot org 2005-10-04 22:58 ---
A library may be compiled with -ffunction-sections. It doesn't mean that all
codes linked against that library have to use -ffunction-sections. For example,
libstdc++ is compiled with -ffunction-sections. Do I have to use it f
--- Comment #3 from pinskia at gcc dot gnu dot org 2005-10-04 22:41 ---
(In reply to comment #2)
> The problem is with -ffunction-sections, we may put a very big cold function
> in
> the .text.hot section and a very hot function in the .text.unlikely section.
> It
> defeats the whole p
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-10-04 21:52 ---
I don't see why this is really a problem. It only effects the gcing sections,
it just means you are not going to remove those functions when used with other
functions which are in the hold/cold section.
--
pinsk
