Bug 9788 - optimization bug with 176.gcc from SPECcpu2000
Summary: optimization bug with 176.gcc from SPECcpu2000
Status: RESOLVED DUPLICATE of bug 9787
Alias: None
Product: gcc
Classification: Unclassified
Component: c (show other bugs)
Version: 3.2.2
: P2 critical
Target Milestone: ---
Assignee: Paolo Carlini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-21 14:16 UTC by thomas.anders
Modified: 2003-06-02 21:18 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description thomas.anders 2003-02-21 14:16:00 UTC 
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.

Release:
gcc version 3.2.2

Environment:
Intel Pentium 4 1.70GHz
SuSE Linux 8.1, Kernel 2.4.19

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").
Comment 1 thomas.anders 2003-02-21 14:16:00 UTC 
Fix:
Yes, please! ;)
Comment 2 Paolo Carlini 2003-02-21 14:29:17 UTC 
*** This bug has been marked as a duplicate of 9787 ***