public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49710] [4.7 Regression] segfault
Date: Tue, 12 Jul 2011 08:56:00 -0000	[thread overview]
Message-ID: <bug-49710-4-FtoEJ4qzo3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49710-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-07-12 08:54:29 UTC ---
Caused by http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172430
but more probably this is just a dup of PR48813, which was for this testcase
latent before.  Honza, any chance you could look at that and PR48813?  The ICE
is in the exact same spot, base_loop is non-NULL, but base_loop->header is
NULL,
as the loop has been marked for removal in delete_basic_block called from
remove_bbs/remove_path during the peeling.  The same remove_path then calls
fix_loop_placements which calls fix_bb_placements which ICEs.
That delete_basic_block is apparently called on the loop->latch bb, which
queues the loop for removal anyway, but loop->header hasn't been removed and
its bb->loop_father still points to the loop that has now header and latch
fields NULL.


  parent reply	other threads:[~2011-07-12  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  4:43 [Bug c/49710] New: segfault regehr at cs dot utah.edu
2011-07-12  7:33 ` [Bug rtl-optimization/49710] segfault jakub at gcc dot gnu.org
2011-07-12  8:51 ` [Bug rtl-optimization/49710] [4.7 Regression] segfault rguenth at gcc dot gnu.org
2011-07-12  8:56 ` jakub at gcc dot gnu.org [this message]
2011-10-10 11:59 ` rguenth at gcc dot gnu.org
2011-12-28 19:11 ` hubicka at gcc dot gnu.org
2011-12-28 19:52 ` hubicka at gcc dot gnu.org
2012-01-03 17:52 ` hubicka at gcc dot gnu.org
2012-01-05 19:26 ` hubicka at gcc dot gnu.org
2012-01-05 19:29 ` hubicka 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-49710-4-FtoEJ4qzo3@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).