public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Brian Kuschak <bkuschak@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10593: -O2 dead-code optimization removes the wrong code
Date: Fri, 02 May 2003 00:46:00 -0000	[thread overview]
Message-ID: <20030502004601.30981.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10593; it has been noted by GNATS.

From: Brian Kuschak <bkuschak@yahoo.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/10593: -O2 dead-code optimization removes the wrong code
Date: Thu, 1 May 2003 17:38:46 -0700 (PDT)

 Read the 'Fix' field.
 
 --- bangerth@dealii.org wrote:
 > Synopsis: -O2 dead-code optimization removes the
 > wrong code
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Fri May  2 00:33:47 2003
 > State-Changed-Why:
 >     2.95 is a very old release. Can you say anything
 > about
 >     whether the problem still occurs with newer
 > versions of
 >     gcc?
 >     
 >     Thanks
 >       Wolfgang
 > 
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10593
 
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com


             reply	other threads:[~2003-05-02  0:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  0:46 Brian Kuschak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-02  0:54 bangerth
2003-05-02  0:46 Brian Kuschak
2003-05-02  0:46 Andrew Pinski
2003-05-02  0:33 bangerth
2003-05-02  0:26 bkuschak

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=20030502004601.30981.qmail@sources.redhat.com \
    --to=bkuschak@yahoo.com \
    --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).