public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: dan.naumov@ofw.fi, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	ljrittle@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: optimization/10030: gcc 3.2(.1) produces broken code with -O2, but not -O
Date: Wed, 26 Mar 2003 10:24:00 -0000	[thread overview]
Message-ID: <20030326102256.7366.qmail@sources.redhat.com> (raw)

Synopsis: gcc 3.2(.1) produces broken code with -O2, but not -O

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Wed Mar 26 10:22:56 2003
Responsible-Changed-Why:
    Mine.  (I lowered the severity: Anything so nebulous with a posted workaround is, by default, not critical!)
State-Changed-From-To: feedback->closed
State-Changed-By: ljrittle
State-Changed-When: Wed Mar 26 10:22:56 2003
State-Changed-Why:
    9 times out of 10, we never hear from these people again.  Please just close ill-formed reports that refer to mega-packages...
    
    General Notes: A compiled program crashing at -O2 but not -O
    does not imply a compiler bug.  This is why someone (you) will
    need to produce a small test case.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10030


             reply	other threads:[~2003-03-26 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 10:24 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 20:11 bangerth
2003-03-11 19:56 dan.naumov

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=20030326102256.7366.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=dan.naumov@ofw.fi \
    --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).