public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/25937] ICE with -O2 -ftree-loop-linear
Date: Tue, 24 Jan 2006 03:15:00 -0000 [thread overview]
Message-ID: <20060124031514.14535.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25937-8649@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from dberlin at gcc dot gnu dot org 2006-01-24 03:15 -------
These ICE's are very hard to fix without real loop distribution. They
basically all concern the perfect nest transformation.
I'm not even sure it's worth attempting to fix them by hacking up the perfect
nest transformation further.
--
dberlin at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC build triplet| |powerpc64-linux
GCC host triplet| |powerpc64-linux
GCC target triplet| |powerpc64-linux
Summary|[4.2 Regression] ICE with - |ICE with -O2 -ftree-loop-
|O2 -ftree-loop-linear |linear
Target Milestone|4.2.0 |---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25937
next prev parent reply other threads:[~2006-01-24 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 1:48 [Bug tree-optimization/25937] New: ICE: Illegal instruction, with valid code uttamp at us dot ibm dot com
2006-01-24 1:58 ` [Bug tree-optimization/25937] " uttamp at us dot ibm dot com
2006-01-24 2:00 ` [Bug tree-optimization/25937] ICE with -O2 -ftree-loop-linear pinskia at gcc dot gnu dot org
2006-01-24 2:18 ` [Bug tree-optimization/25937] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-01-24 3:15 ` dberlin at gcc dot gnu dot org [this message]
2006-01-25 23:14 ` [Bug tree-optimization/25937] " uttamp at us dot ibm dot com
2006-03-23 9:35 ` rguenth at gcc dot gnu dot org
2006-05-18 5:50 ` pinskia 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=20060124031514.14535.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).