This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/10221: gcc -O9 will introduce wrong asembler?
- From: steven at gcc dot gnu dot org
- To: eoo at chess dot nl, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 26 Mar 2003 14:02:35 -0000
- Subject: Re: optimization/10221: gcc -O9 will introduce wrong asembler?
- Reply-to: steven at gcc dot gnu dot org, eoo at chess dot nl, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: gcc -O9 will introduce wrong asembler?
State-Changed-From-To: open->feedback
State-Changed-By: steven
State-Changed-When: Wed Mar 26 14:02:34 2003
State-Changed-Why:
Hi,
Thanks for the problem report. Unfortunately, I
am unable to reproduce the bug with the code you
attached:
1) The RELEASE and DEBUG codes you talk about are
not in the preprocessed source.
2) The code you provided seems to rely on other
compilation units, i.e. there are undefined
references at link time.
Can you produce a smaller test case, or at least one
without external references?
Oh, and I suppose you see this problem with -O3 as
well? The highest optimization level for GCC is -O3,
if you do -On, n>3, nothing extra happens.
Greetz
Steven
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10221