public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42644] New: wrong code for -fgraphite-identify in 183.equake
Date: Thu, 07 Jan 2010 01:42:00 -0000 [thread overview]
Message-ID: <bug-42644-4503@http.gcc.gnu.org/bugzilla/> (raw)
Test 183.equake from SPEC CPU2000 gets wrong results on powerpc64-linux (-m32
or -m64) when compiled with either "-O2 -fgraphite-identity" or "-O2
-floop-parallelize-all". I'll attach an executable testcase that demonstrates
the failure. Test 178.galgel fails with the same options but I haven't
investigated it.
The failure starts with the merge from the Graphite branch for r150301. With
options "-O2 -fgraphite-identity" the minimized testcase and the two CPU2000
tests pass with r150248, the last revision before that merge that builds on
powerpc64-linux. They also pass with GCC 4.4.2 with "-O2 -fgraphite-identity".
--
Summary: wrong code for -fgraphite-identify in 183.equake
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: janis at gcc dot gnu dot org
GCC target triplet: powerpc64-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42644
next reply other threads:[~2010-01-07 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 1:42 janis at gcc dot gnu dot org [this message]
2010-01-07 1:43 ` [Bug tree-optimization/42644] " janis at gcc dot gnu dot org
2010-01-07 11:49 ` [Bug tree-optimization/42644] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-01-07 14:55 ` rguenth at gcc dot gnu dot org
2010-01-14 8:45 ` spop at gcc dot gnu dot org
2010-01-20 15:26 ` uramakrishna at gmail dot com
2010-01-20 15:51 ` grosser at gcc dot gnu dot org
2010-03-08 17:55 ` [Bug tree-optimization/42644] [4.5 Regression][graphite] " spop at gcc dot gnu dot org
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-42644-4503@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).