This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/14470] x86 optimizer error (?)
- From: "zack at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Mar 2004 05:30:00 -0000
- Subject: [Bug c/14470] x86 optimizer error (?)
- References: <20040307221314.14470.lvoge@cs.vu.nl>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From zack at gcc dot gnu dot org 2004-03-08 05:29 -------
I can reproduce the bug with 3.2, 3.3, 3.4, and mainline (but not with 2.95)
using unmodified FSF sources. The problem y'all are probably having, is that
this program may or may not crash depending on stack layout. I've got an a.out
that reproducibly crashes on one machine and not on another.
I'm going to attach a modified test program which exhibits variable output
instead of crashing.
$ ./a.out-O0
1024 1025 0
$ ./a.out-O2
1024 1024 1
$ ./xgcc -B./ -v
Reading specs from ./specs
Configured with: /home/zack/src/gcc/3.4/vanilla/configure
--prefix=/home/zack/src/i/gcc_ni --disable-checking --enable-threads
--enable-languages=c,c++ --disable-nls
Thread model: posix
gcc version 3.4.0 20040301 (prerelease)
(The -O0 output is correct.)
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2004-03-08 05:29:59
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14470