public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: re: c/2466 Testsuite failure gcc.c-torture/execute/loop-2b.c -O2
Date: Tue, 01 May 2001 18:06:00 -0000 [thread overview]
Message-ID: <20010502010601.5576.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/2466; it has been noted by GNATS.
From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>,
"'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>
Cc: "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>
Subject: re: c/2466 Testsuite failure gcc.c-torture/execute/loop-2b.c -O2
Date: Wed, 2 May 2001 00:58:36 -0000
Richard Henderson [rth@redhat.com] tells me:
> That bug fails off and on depending on
> the optimizers that run before and how good a job they do.
> The bug wasn't fixed for 2.95, merely obscured. Nor was
> it really broken by the patch you reference in the PR.
so this PR has been analysed, and I guess it can be downgraded or even
closed.
next reply other threads:[~2001-05-01 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 18:06 Billinghurst, David (CRTS) [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 10:52 c/2466: " neil
2001-04-02 23:36 David.Billinghurst
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=20010502010601.5576.qmail@sourceware.cygnus.com \
--to=david.billinghurst@riotinto.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).