public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46190] New: ICE in vect_enhance_data_refs_alignment when building fma3d
Date: Tue, 26 Oct 2010 22:08:00 -0000 [thread overview]
Message-ID: <bug-46190-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46190
Summary: ICE in vect_enhance_data_refs_alignment when building
fma3d
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: pthaugen@gcc.gnu.org
CC: rguenth@gcc.gnu.org
Host: powerpc64-linux
Target: powerpc64-linux
Build: powerpc64-linux
Created attachment 22166
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22166
testcase
Looks like the fix for PR45720 (rev165832) causes an ICE when trying to build
CPU2000 benchmark fma3d. Benchmark file is fma1.f90, reduced testcase is
attatched.
> gfortran -c -O2 -ftree-vectorize -mcpu=power7 err.f90
err.f90: In function `spot_weld_initialization':
err.f90:1:0: internal compiler error: in vect_enhance_data_refs_alignment, at
tree-vect-data-refs.c:1550
next reply other threads:[~2010-10-26 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 22:08 pthaugen at gcc dot gnu.org [this message]
2010-10-27 20:48 ` [Bug tree-optimization/46190] [4.6 Regression] " rguenth at gcc dot gnu.org
2010-10-29 12:54 ` rguenth at gcc dot gnu.org
2010-11-02 15:14 ` rguenth at gcc dot gnu.org
2010-11-02 19:36 ` pthaugen at gcc dot gnu.org
2010-11-02 20:28 ` pthaugen at gcc dot gnu.org
2010-11-03 10:57 ` rguenth at gcc dot gnu.org
2010-11-03 13:31 ` rguenth at gcc dot gnu.org
2010-11-03 13:32 ` rguenth at gcc dot gnu.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-46190-4@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).