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 middle-end/40386] wrong code generation for SPEC CPU2000's 189.lucas with -O1 -fno-ira-share-spill-slots
Date: Tue, 09 Jun 2009 13:35:00 -0000	[thread overview]
Message-ID: <20090609133512.1230.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40386-13613@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from kenneth dot hoste at elis dot ugent dot be  2009-06-09 13:35 -------
I did some more experiments, and have some more details to share.

It seems the problem with lucas only occurs with the SVN head of the 4.4 branch
I'm working on (r148268), and not with the 4.4.0 release.

However, a similar problem is occuring with the 172.mgrid benchmark, and this
_is_ occuring both with the 4.4.0 release and with revision 148268 of the 4.4
branch.

Again, -O1 -fno-ira-share-spill-slots leads to a binary not producing correct
output (but there's not noticeable crash of the benchmark this time). Using -O1
yields no problems though.

The SPEC framework reports the below as a diff between the expected and
observed output for mgrid, and considers the difference to be serious enough to
report the run to be invalid.

0019:      0.103090E-02
          -0.907513E-03
                      ^
0020:      0.103090E-02
          -0.907513E-03
                      ^
0021:      0.184495E-02
           0.261074E-02
                      ^
0022:      0.184495E-02
           0.261074E-02
                      ^
0023:      0.366257E-03
          -0.677032E-04
                      ^
0024:      0.366257E-03
          -0.677032E-04
                      ^
0025:      0.436098E-03
           0.179609E-03
                      ^
0026:      0.436098E-03
           0.179609E-03
                      ^
0027:      0.442029E-03
           0.212079E-03
                      ^
0028:      0.442029E-03
           0.212079E-03
                      ^
0029:      0.442962E-03
           0.217171E-03
                      ^


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40386


  parent reply	other threads:[~2009-06-09 13:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 12:07 [Bug fortran/40386] New: " kenneth dot hoste at elis dot ugent dot be
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 [this message]
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=20090609133512.1230.qmail@sourceware.org \
    --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).