public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: thomas.anders@blue-cable.de
To: gcc-gnats@gcc.gnu.org
Subject: c/9788: optimization bug with 176.gcc from SPECcpu2000
Date: Fri, 21 Feb 2003 14:16:00 -0000 [thread overview]
Message-ID: <20030221141213.22053.qmail@sources.redhat.com> (raw)
>Number: 9788
>Category: c
>Synopsis: optimization bug with 176.gcc from SPECcpu2000
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Feb 21 14:16:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Thomas Anders
>Release: gcc version 3.2.2
>Organization:
>Environment:
Intel Pentium 4 1.70GHz
SuSE Linux 8.1, Kernel 2.4.19
>Description:
The 176.gcc benchmark from the latest SPECcpu2000 V1.2 benchmark suite (www.spec.org/osg/cpu2000/) gives wrong results ("miscompare") when using optimization levels 1, 2 or 3 (e.g. "-O3") and "-march=pentium4" with gcc 3.2.2 (Release). Unfortunately I can't provide the source code here since it's covered under SPEC's license. A SPEC licensee (from SuSE, RedHat and friends) should be looking at this issue.
>How-To-Repeat:
Compile the 176.gcc benchmark from the SPECcpu2000 benchmark suite (www.spec.org/osg/cpu2000/) with OPTIMIZE="-O3 -march=pentium4" using gcc 3.2.2 (Release), then run it the usual way ("runspec").
>Fix:
Yes, please! ;)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-02-21 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 14:16 thomas.anders [this message]
2003-02-21 14:29 paolo
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=20030221141213.22053.qmail@sources.redhat.com \
--to=thomas.anders@blue-cable.de \
--cc=gcc-gnats@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).