public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: bkuschak@yahoo.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/10593: -O2 dead-code optimization removes the wrong code Date: Fri, 02 May 2003 00:54:00 -0000 [thread overview] Message-ID: <20030502005434.29743.qmail@sources.redhat.com> (raw) Synopsis: -O2 dead-code optimization removes the wrong code State-Changed-From-To: feedback->closed State-Changed-By: bangerth State-Changed-When: Fri May 2 00:54:34 2003 State-Changed-Why: No, sorry, I missed the "Fix" field. I fear, you're out of luck: we just abandoned the 3.2 branch, and before that the 3.0 branch. Nobody's going to fix bugs in 2.95 any more, unless -- maybe -- being paid for that. In any case, I don't think we should keep open bug reports for things we know are working now. Sorry Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10593
next reply other threads:[~2003-05-02 0:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-02 0:54 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-02 0:46 Andrew Pinski 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=20030502005434.29743.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=bkuschak@yahoo.com \ --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: 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).