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 c++/55405] ICE with optimization
Date: Sun, 25 Nov 2012 11:11:00 -0000	[thread overview]
Message-ID: <bug-55405-4-Qfd51x2HYO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55405-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55405

Mikael Pettersson <mikpe at it dot uu.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikpe at it dot uu.se

--- Comment #2 from Mikael Pettersson <mikpe at it dot uu.se> 2012-11-25 11:11:35 UTC ---
The ICE at -O3 was first silenced for 4.7 by r171450:
http://gcc.gnu.org/ml/gcc-cvs/2011-03/msg00874.html,
when Richard Biener added an FRE pass after early SRA.

At that point the ICE still occurs with -O3 -fno-tree-fre.

The ICE at -O3 -fno-tree-fre was then silenced for 4.7 by r181014:
http://gcc.gnu.org/ml/gcc-cvs/2011-11/msg00300.html,
a missed-optimization patch.

The ICE before r181014 occurs because except.c:emit_to_new_bb_before is called
on an insn whose BLOCK_FOR_INSN is NULL, but that NULL pointer is
unconditionally dereferenced causing a SEGV.  I don't see a sane way of
handling that locally.


  parent reply	other threads:[~2012-11-25 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  0:15 [Bug c++/55405] New: " cas43 at cs dot stanford.edu
2012-11-20  0:23 ` [Bug c++/55405] " paolo.carlini at oracle dot com
2012-11-25 11:11 ` mikpe at it dot uu.se [this message]
2012-11-25 11:32 ` [Bug tree-optimization/55405] " paolo.carlini at oracle dot com
2014-12-11 12:48 ` mpolacek 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-55405-4-Qfd51x2HYO@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).