public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41305] New: ICE with -O3 -floop-interchange
Date: Tue, 08 Sep 2009 09:16:00 -0000 [thread overview]
Message-ID: <bug-41305-87@http.gcc.gnu.org/bugzilla/> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
The following testcase ICEs on x86_64-linux on branches/gcc-4_4-branch with -O3
-floop-interchange:
Unable to coalesce ssa_names 99 and 106 which are marked as MUST COALESCE.
xi$data_$size__99(ab) and xi$data_$size__106(ab)
/tmp/rh520785.ii: In function ‘void foo(int)’:
/tmp/rh520785.ii:321: internal compiler error: SSA corruption
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Couldn't reproduce this on the trunk, but that doesn't mean the bug isn't
latent there. Doesn't reproduce without -floop-interchange, so I assume it is
graphite which is at fault here.
--
Summary: ICE with -O3 -floop-interchange
Product: gcc
Version: 4.4.2
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jakub at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41305
next reply other threads:[~2009-09-08 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 9:16 jakub at gcc dot gnu dot org [this message]
2009-09-08 9:17 ` [Bug tree-optimization/41305] " jakub at gcc dot gnu dot org
2009-10-15 16:38 ` spop at gcc dot gnu dot org
2009-12-23 18:11 ` spop at gcc dot gnu dot org
2009-12-23 18:15 ` [Bug c++/41305] Infinite recursion with g++ at -O0 spop at gcc dot gnu dot org
2009-12-23 20:12 ` hjl dot tools at gmail dot com
2009-12-23 20:12 ` hjl dot tools at gmail dot com
2009-12-24 14:07 ` jason at gcc dot gnu dot org
2009-12-24 21:03 ` jason at gcc dot gnu dot org
2009-12-24 21:46 ` jason at gcc dot gnu dot org
2009-12-28 17:19 ` hjl 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-41305-87@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).