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/54902] [4.7 Regression], ICE (segfault) building on arm-linux-gnueabi
Date: Sat, 13 Oct 2012 15:39:00 -0000 [thread overview]
Message-ID: <bug-54902-4-141ypiQoPN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54902-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54902
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2012-10-13 15:39:25 UTC ---
I can reproduce the ICE with gcc-4.7.2 on armv5tel-linux-gnueabi, sparc64-linux
-m32, x86_64-linux -m32, and m68k-linux. I haven't checked any other targets.
The ICE stopped on trunk with Richard B's "Make gsi_remove return whether EH
cleanup is required" patch in r186159:
http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00202.html
http://gcc.gnu.org/ml/gcc-cvs/2012-04/msg00108.html
Backporting r186159 and the follow-up fix in r186164 to gcc-4.7.2 eliminates
the ICE there for the four targets mentioned above.
The description of Richard's patch makes it sound more like a cleanup than a
bug fix, so I'm not sure if it actually fixes the bug or just masks it.
next prev parent reply other threads:[~2012-10-13 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:34 [Bug target/54902] New: " doko at gcc dot gnu.org
2012-10-12 9:37 ` [Bug target/54902] " rguenth at gcc dot gnu.org
2012-10-12 9:59 ` doko at gcc dot gnu.org
2012-10-13 15:39 ` mikpe at it dot uu.se [this message]
2012-10-23 5:35 ` zhenqiang.chen at linaro dot org
2012-10-24 13:41 ` rguenth at gcc dot gnu.org
2012-10-24 13:59 ` rguenth at gcc dot gnu.org
2012-10-25 11:06 ` rguenth at gcc dot gnu.org
2012-10-25 11:16 ` rguenth at gcc dot gnu.org
2012-10-25 11: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-54902-4-141ypiQoPN@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).