public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> 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.31000.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10593; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: bangerth@dealii.org, bkuschak@yahoo.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Andrew Pinski <pinskia@physics.uc.edu> Subject: Re: optimization/10593: -O2 dead-code optimization removes the wrong code Date: Thu, 1 May 2003 20:40:51 -0400 Did you read the fix part: Problem does not occur with gcc-3.2.=A0 But I really want to fix this in = =20 2.95.3. Thanks, Andrew Pinski On Thursday, May 1, 2003, at 20:33 US/Eastern, bangerth@dealii.org =20 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=3Dview%20audit-=20 > trail&database=3Dgcc&pr=3D10593 > >
next 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 Andrew Pinski [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 Brian Kuschak 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.31000.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --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: linkBe 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).