public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: steven@gcc.gnu.org
To: eoo@chess.nl, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/10221: gcc -O9 will introduce wrong asembler?
Date: Wed, 26 Mar 2003 14:15:00 -0000	[thread overview]
Message-ID: <20030326140235.26227.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2003-03-26 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 14:15 steven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 14:18 Erik Oosterom
2003-03-26 13:01 eoo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030326140235.26227.qmail@sources.redhat.com \
    --to=steven@gcc.gnu.org \
    --cc=eoo@chess.nl \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).