public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: optimization/1762, please reopen
Date: Mon, 25 Jun 2001 11:16:00 -0000 [thread overview]
Message-ID: <20010625181602.17536.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR optimization/1762; it has been noted by GNATS.
From: Richard Henderson <rth@redhat.com>
To: Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: rth@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
gcc-bugs@gcc.gnu.org
Subject: Re: optimization/1762, please reopen
Date: Mon, 25 Jun 2001 11:08:34 -0700
On Mon, Jun 25, 2001 at 06:57:58PM +0200, Reichelt wrote:
> I'm afraid the bug reappeared with the 3.0 release.
> So, please reopen the PR.
The test case still passes for me. Is the test not in fact
representative of your code?
r~
next reply other threads:[~2001-06-25 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 11:16 Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-26 4:36 Reichelt
2001-06-25 9: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=20010625181602.17536.qmail@sourceware.cygnus.com \
--to=rth@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=rth@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).