public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43437] ICE in CSE, during libgcc build
Date: Tue, 20 Dec 2011 23:33:00 -0000 [thread overview]
Message-ID: <bug-43437-4-Oo9cdrFNW4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43437-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43437
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #19 from Mikael Pettersson <mikpe at it dot uu.se> 2011-12-20 23:27:23 UTC ---
The real cause of the ICE in the second test case is Alexandre Oliva's PR
debug/43092 + PR rtl-optimization/43494 fix in r169782:
http://gcc.gnu.org/ml/gcc-cvs/2011-02/msg00325.html
The ICE is masked when the PR37273 missed-optimization fix is present, i.e.
from r169231 to r170199 (exclusive), and from r171111 on current trunk. But
4.6 branch doesn't have the PR37273 fix, so the ICE does occur there.
next prev parent reply other threads:[~2011-12-20 23:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43437-4@http.gcc.gnu.org/bugzilla/>
2011-12-18 22:00 ` tg at mirbsd dot org
2011-12-18 22:02 ` tg at mirbsd dot org
2011-12-18 22:15 ` tg at mirbsd dot org
2011-12-19 0:23 ` mikpe at it dot uu.se
2011-12-19 0:35 ` tg at mirbsd dot org
2011-12-20 0:13 ` mikpe at it dot uu.se
2011-12-20 9:49 ` mikpe at it dot uu.se
2011-12-20 15:28 ` mikpe at it dot uu.se
2011-12-20 23:33 ` mikpe at it dot uu.se [this message]
2012-02-07 21:25 ` tg at mirbsd dot org
2012-02-18 17:04 ` mikpe at it dot uu.se
2012-02-19 1:23 ` tg at mirbsd dot org
2012-03-25 12:01 ` aoliva at gcc dot gnu.org
2010-03-19 1:24 [Bug target/43437] New: build error segher at gcc dot gnu dot org
2010-03-19 2:25 ` [Bug target/43437] ICE in CSE, during libgcc build segher at gcc dot gnu dot org
2010-03-19 15:49 ` aldyh at gcc dot gnu dot org
2010-03-19 15:58 ` aldyh at gcc dot gnu dot org
2010-03-19 17:35 ` jakub at gcc dot gnu dot org
2010-03-19 18:41 ` aldyh at gcc dot gnu dot org
2010-03-19 20:37 ` jakub at gcc dot gnu dot org
2010-03-19 21:14 ` jakub at gcc dot gnu dot org
2010-03-22 16:13 ` law at redhat dot com
2010-07-23 11:48 ` jakub at gcc dot gnu dot org
2010-07-23 11:57 ` segher 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-43437-4-Oo9cdrFNW4@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).