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/42637] New: wrong code for -floop-interchange -ftree-loop-distribution
Date: Wed, 06 Jan 2010 18:25:00 -0000 [thread overview]
Message-ID: <bug-42637-4503@http.gcc.gnu.org/bugzilla/> (raw)
As mentioned in PR 42334, 200.sixtrack from SPEC CPU2000 started getting wrong
answers on powerpc64-linux with the Graphite merge at r140301 when compiled
with "-O2 -floop-interchange -ftree-loop-distribution". The loop that is
miscompiled is:
real*8 rt(6,6),r(6,6),rtt(6,6)
do i=1,6
do j=1,6
do ia=1,6
rtt(i,ia)=rt(i,j)*r(j,ia)+rtt(i,ia)
end do
end do
end do
I'll attach a complete executable testcase that demonstrates the failure.
This testcase, and 200.sixtrack, pass when compiled with these options with GCC
4.4.2 and with trunk r150248 (the last trunk revision before r150301 that
builds on powerpc64-linux).
--
Summary: wrong code for -floop-interchange -ftree-loop-
distribution
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=42637
next reply other threads:[~2010-01-06 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 18:25 janis at gcc dot gnu dot org [this message]
2010-01-06 18:27 ` [Bug tree-optimization/42637] " janis at gcc dot gnu dot org
2010-01-06 19:02 ` [Bug tree-optimization/42637] [4.5 Regression][graphite] " rguenth at gcc dot gnu dot org
2010-01-06 19:19 ` dominiq at lps dot ens dot fr
2010-01-07 14:54 ` rguenth at gcc dot gnu dot org
2010-01-14 8:41 ` spop at gcc dot gnu dot org
2010-01-15 1:20 ` spop at gcc dot gnu dot org
2010-01-16 22:17 ` spop at gcc dot gnu dot org
2010-01-16 22:31 ` spop at gcc dot gnu dot org
2010-02-06 7:14 ` spop at gcc dot gnu dot org
2010-02-06 16:33 ` spop at gcc dot gnu dot org
2010-02-06 16:44 ` spop at gcc dot gnu dot org
2010-02-06 17:42 ` spop at gcc dot gnu dot org
2010-02-06 17:42 ` 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-42637-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).