public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: target/2427
Date: Tue, 05 Jun 2001 16:36:00 -0000 [thread overview]
Message-ID: <20010605233600.25654.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR target/2427; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <mmitchel@gcc.gnu.org>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: target/2427
Date: Wed, 6 Jun 2001 00:31:34 +0100 (BST)
On 5 Jun 2001 mmitchel@gcc.gnu.org wrote:
> Please identify all of the the specific failures -- both
> those that appear with -mcpu=k6 and -mcpu=athlon. The former
> are high-priority; the latter are not. Until we know
> which failures are which, we cannot know when to downgrade
> the report.
The following are the failures with 3.0:
loop-2b.c -mcpu=k6 -O3 -fomit-frame-pointer
loop-2b.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-loops
loop-2b.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
loop-2b.c -mcpu=k6 -O3 -g
loop-2b.c -mcpu=k6 -Os
loop-2b.c -mcpu=k6 -O2
loop-2b.c -mcpu=athlon -O3 -fomit-frame-pointer
loop-2b.c -mcpu=athlon -O3 -fomit-frame-pointer -funroll-loops
loop-2b.c -mcpu=athlon -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
loop-2b.c -mcpu=athlon -O3 -g
loop-2b.c -mcpu=athlon -Os
loop-2b.c -mcpu=athlon -O2
loop-2e.c -mcpu=athlon -O3 -fomit-frame-pointer
loop-2e.c -mcpu=athlon -O3 -g
loop-2e.c -mcpu=athlon -Os
loop-2e.c -mcpu=athlon -O2
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-loops
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
loop-3c.c -mcpu=k6 -O3 -g
loop-3c.c -mcpu=k6 -Os
loop-3c.c -mcpu=k6 -O2
loop-3c.c -mcpu=athlon -O3 -fomit-frame-pointer
loop-3c.c -mcpu=athlon -O3 -fomit-frame-pointer -funroll-loops
loop-3c.c -mcpu=athlon -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
loop-3c.c -mcpu=athlon -O3 -g
loop-3c.c -mcpu=athlon -Os
loop-3c.c -mcpu=athlon -O2
Of these, the following are regressions:
loop-2b.c -mcpu=k6 -Os
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-loops
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
loop-3c.c -mcpu=k6 -O3 -g
loop-3c.c -mcpu=k6 -Os
loop-3c.c -mcpu=k6 -O2
Two testcases appear to hang:
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-loops
loop-3c.c -mcpu=k6 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
The rest of the failures abort quickly.
PR target/656 also discusses the same problem.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2001-06-05 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 16:36 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-05 16:16 target/2427 mmitchel
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=20010605233600.25654.qmail@sourceware.cygnus.com \
--to=jsm28@cam.ac.uk \
--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).