public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6189: Regression from 3.0.x: g++ -O3 generates wrong code Date: Mon, 10 Jun 2002 07:16:00 -0000 [thread overview] Message-ID: <20020610141606.11440.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6189; it has been noted by GNATS. From: Jason Merrill <jason@redhat.com> To: Reichelt <reichelt@igpm.rwth-aachen.de> Cc: gcc-gnats@gcc.gnu.org Subject: Re: optimization/6189: Regression from 3.0.x: g++ -O3 generates wrong code Date: Mon, 10 Jun 2002 15:06:07 +0100 >>>>> "Reichelt" == Reichelt <reichelt@igpm.rwth-aachen.de> writes: > Is there any reason why you did not close the PR? The problem seems to > be fixed in gcc 3.1 as well as in mainline (gcc 3.2 20020610). Because I thought we might want to fix it in a hypothetical 3.0.5 release. Jason
next reply other threads:[~2002-06-10 14:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-10 7:16 Jason Merrill [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-28 13:22 reichelt 2002-06-10 5:56 Reichelt 2002-04-05 7:56 reichelt
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=20020610141606.11440.qmail@sources.redhat.com \ --to=jason@redhat.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: 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).