------- Comment #35 from rguenth at gcc dot gnu dot org 2009-01-19 10:29
-------
I can reproduce the issue with the testcase in comment #27 on x86_64-linux
with -m32 -O2 vs. -m32 -O.
It can be reduced to the effect of -fschedule-insns2 and -fforward-propagate
(disabling either on -O2 -fno-strict-aliasing is enough to fix the failure,
enabling both is enough to trigger the failure with -O).
I didn't track down which asm difference makes it fail, but there are some
changes across calls which look dubious. CCing Paolo and Steven ...
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stevenb dot gcc at gmail dot
| |com, bonzini at gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |wrong-code
Last reconfirmed|0000-00-00 00:00:00 |2009-01-19 10:29:50
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38868
