public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eres at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41498] ICE with graphite flags on trunk
Date: Tue, 01 Dec 2009 13:45:00 -0000 [thread overview]
Message-ID: <20091201134548.19497.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41498-13229@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from eres at il dot ibm dot com 2009-12-01 13:45 -------
(In reply to comment #5)
> test.f works on amd64-linux on the graphite branch.
> I am doing the merge of the graphite branch to trunk,
> and this should be fixed then.
Running test.f using trunk -r154872 on powerpc64-suse-linux gives the
following:
(this message also appears when running SPEC2006 benchmarks)
/home/eres/mainline_45/build/bin/gfortran -c -m64 -O3 -mcpu=power6
-ffast-math -maltivec -fno-loop-parallelize-all -fgraphite -fno-loop-block
-fno-loop-interchange -fno-loop-strip-mine -fgraphite-identity -ftree-vectorize
test.f
f951: sorry, unimplemented: Graphite loop optimizations cannot be used
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41498
next prev parent reply other threads:[~2009-12-01 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 6:45 [Bug tree-optimization/41498] New: ICE with graphite flags eres at il dot ibm dot com
2009-09-29 9:49 ` [Bug tree-optimization/41498] ICE with graphite flags on trunk rguenth at gcc dot gnu dot org
2009-10-22 19:00 ` spop at gcc dot gnu dot org
2009-10-25 11:55 ` eres at il dot ibm dot com
2009-10-25 14:31 ` eres at il dot ibm dot com
2009-10-25 15:32 ` spop at gcc dot gnu dot org
2009-12-01 13:45 ` eres at il dot ibm dot com [this message]
2009-12-01 14:09 ` rguenth 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=20091201134548.19497.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).