public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebpop at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/42181] [4.5 Regression][graphite] -fgraphite-identity miscompiles air.f90
Date: Sun, 21 Mar 2010 16:28:00 -0000 [thread overview]
Message-ID: <20100321162812.6917.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42181-11113@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
------- Comment #26 from sebpop at gmail dot com 2010-03-21 16:28 -------
Subject: Re: [4.5 Regression][graphite]
-fgraphite-identity miscompiles air.f90
On Sat, Mar 20, 2010 at 05:45, dominiq at lps dot ens dot fr wrote:
> Do you understand why graphite does not detect that the loop for [scat_1+1,
> T_10-2] depends on the one for [0, scat_1-1]?
Graphite does know this, but it does not ask CLooG to generate
[0, scat_1-1] after [scat_1+1, T_10-2], however CLooG does
generate it, so I am thinking that this is a problem in CLooG.
> Second question why does graphite exchange the order of the split loops?
>
CLooG does that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42181
next prev parent reply other threads:[~2010-03-21 16:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 2:53 [Bug middle-end/42181] New: -fgraphite-identity miscompiles or ICEs on air.f90 howarth at nitro dot med dot uc dot edu
2009-11-26 17:03 ` [Bug middle-end/42181] " jv244 at cam dot ac dot uk
2009-11-26 17:04 ` jv244 at cam dot ac dot uk
2009-11-26 17:05 ` [Bug middle-end/42181] [4.5 Regression] " jv244 at cam dot ac dot uk
2009-11-27 11:32 ` rguenth at gcc dot gnu dot org
2009-12-14 19:03 ` spop at gcc dot gnu dot org
2009-12-14 19:03 ` spop at gcc dot gnu dot org
2009-12-23 7:50 ` spop at gcc dot gnu dot org
2009-12-24 0:14 ` howarth at nitro dot med dot uc dot edu
2009-12-24 0:15 ` howarth at nitro dot med dot uc dot edu
2009-12-24 0:18 ` howarth at nitro dot med dot uc dot edu
2009-12-24 0:20 ` howarth at nitro dot med dot uc dot edu
2009-12-24 8:13 ` dominiq at lps dot ens dot fr
2010-01-14 16:57 ` trifunovic at gcc dot gnu dot org
2010-01-14 19:25 ` spop at gcc dot gnu dot org
2010-02-06 17:44 ` [Bug middle-end/42181] [4.5 Regression][graphite] " spop at gcc dot gnu dot org
2010-03-08 23:09 ` [Bug middle-end/42181] [4.5 Regression][graphite] -fgraphite-identity miscompiles air.f90 howarth at nitro dot med dot uc dot edu
2010-03-08 23:16 ` spop at gcc dot gnu dot org
2010-03-09 2:26 ` howarth at nitro dot med dot uc dot edu
2010-03-09 2:34 ` howarth at nitro dot med dot uc dot edu
2010-03-09 2:35 ` howarth at nitro dot med dot uc dot edu
2010-03-09 2:37 ` howarth at nitro dot med dot uc dot edu
2010-03-09 3:45 ` howarth at nitro dot med dot uc dot edu
2010-03-09 3:49 ` howarth at nitro dot med dot uc dot edu
2010-03-09 13:32 ` dominiq at lps dot ens dot fr
2010-03-09 22:31 ` spop at gcc dot gnu dot org
2010-03-14 11:40 ` dominiq at lps dot ens dot fr
2010-03-20 10:45 ` dominiq at lps dot ens dot fr
2010-03-21 16:28 ` Sebastian Pop
2010-03-21 16:28 ` sebpop at gmail dot com [this message]
2010-03-23 20:08 ` spop at gcc dot gnu dot org
2010-03-23 21:24 ` spop at gcc dot gnu dot org
2010-03-23 21:28 ` spop at gcc dot gnu dot org
2010-03-24 20:18 ` spop at gcc dot gnu dot org
2010-03-24 21:35 ` howarth at nitro dot med dot uc dot edu
2010-03-25 17:43 ` Sebastian Pop
2010-03-26 9:58 ` Richard Guenther
2010-03-25 17:44 ` sebpop at gmail dot com
2010-03-26 9:58 ` rguenther at suse dot de
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=20100321162812.6917.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).