public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kenneth dot hoste at elis dot ugent dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40386] New: wrong code generation for SPEC CPU2000's 189.lucas with -O1 -fno-ira-share-spill-slots
Date: Tue, 09 Jun 2009 12:07:00 -0000 [thread overview]
Message-ID: <bug-40386-13613@http.gcc.gnu.org/bugzilla/> (raw)
I'm observing a wrong code generation bug with the 189.lucas benchmark in SPEC
CPU2000.
When the Fortran benchmark is being compiled with -O1
-fno-ira-share-spill-slots, the benchmark outputs the following:
iteration= 2 000000000000000E
iteration= 3 00000000000000C2
iteration= 4 0000000000009302
iteration= 5 00000000546B4C02
iteration= 6 1BD696D9F03D3002
M75460003 Roundoff warning on iteration 7 maxerr = 0.499999970088
FATAL ERROR...Halting execution.
When compiled with -O1, this is (part of) the output (which is correct, as
specified by the CPU2000 framework):
iteration= 2 000000000000000E
iteration= 3 00000000000000C2
iteration= 4 0000000000009302
iteration= 5 00000000546B4C02
iteration= 6 1BD696D9F03D3002
iteration= 7 8CC88407A9F4C002
iteration= 8 55599F9D37D30002
<snip>
iteration= 122 E9639F5835FD3C2C
exponent residue
75460003 DDD9C8B13BCB64AE
I'm sorry I'm unable to provide a self-contained testcase for this, but I know
little about Fortran. I hope someone else can jump in and provide a testcase
for me.
--
Summary: wrong code generation for SPEC CPU2000's 189.lucas with
-O1 -fno-ira-share-spill-slots
Product: gcc
Version: 4.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: kenneth dot hoste at elis dot ugent dot be
GCC build triplet: linux, x86-64
GCC host triplet: linux, x86-64
GCC target triplet: linux, x86-64
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40386
next reply other threads:[~2009-06-09 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 12:07 kenneth dot hoste at elis dot ugent dot be [this message]
2009-06-09 12:25 ` [Bug middle-end/40386] " burnus at gcc dot gnu dot org
2009-06-09 13:35 ` kenneth dot hoste at elis dot ugent dot be
2009-06-09 14:12 ` kenneth dot hoste at elis dot ugent dot be
2009-06-09 14:22 ` rguenth at gcc dot gnu dot org
2009-06-09 14:31 ` kenneth dot hoste at elis dot ugent dot be
2009-06-09 14:52 ` kenneth dot hoste at elis dot ugent dot be
2010-04-12 13:47 ` [Bug middle-end/40386] wrong code generation for several SPEC CPU2000 benchmarks (lucas, mgrid, face, applu, apsi) " zsojka at seznam dot cz
2010-04-12 18:55 ` zsojka at seznam dot cz
2010-09-08 17:44 ` vmakarov at redhat dot com
2010-09-09 13:43 ` vmakarov at gcc dot gnu dot org
2010-09-09 13:47 ` vmakarov at gcc dot gnu dot org
2010-09-09 13:52 ` vmakarov at gcc dot gnu dot org
2010-09-15 0:05 ` zsojka at seznam dot cz
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=bug-40386-13613@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).