This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/12199] [3.3-hammer regression] long double miscompilation in gsl/amd64
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Sep 2003 00:52:48 -0000
- Subject: [Bug optimization/12199] [3.3-hammer regression] long double miscompilation in gsl/amd64
- References: <20030906231705.12199.gbeauchesne@mandrakesoft.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12199
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC host triplet|x86_64-unknown-linux-gnu |
GCC target triplet| |x86_64-unknown-linux-gnu
Keywords| |wrong-code
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-09-07 00:52 -------
I think the reason why with -O2, it is exhausted, is because check and (I think fabs, might have
already) gets inlined because unit-at-a-time is enabled on the 3.3-hammer branch (and the
mainline also) at -O2 and above.
It would be nice to know if this bug is also on the mainline.
Also what happens if you add __attribute__((__no_inline__)) to the function check, does it still
create wrong code?