public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/65233] [5 Regression] ICE (segfault) on arm-linux-gnueabihf and aarch64-linux-gnu
Date: Mon, 02 Mar 2015 05:49:00 -0000	[thread overview]
Message-ID: <bug-65233-4-5s8rJW7Hzv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65233-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65233

--- Comment #17 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
FWIW, the removal happens by virtue of:

  /* The hash table traversals above created the duplicate blocks (and the
     statements within the duplicate blocks).  This loop creates PHI nodes for
     the duplicated blocks and redirects the incoming edges into BB to reach
     the duplicates of BB.  */
  redirection_data->traverse <ssa_local_info_t *, ssa_redirect_edges>
                (&local_info);

and right after the PHI is getting cleared, the BB has:

<bb 48>:
 pred:      
# .MEM_34 = PHI <>
# SR.33_45 = PHI <>
# SR.32_86 = PHI <>
# DEBUG this => D#8
goto <bb 47>;
 succ:       47 [69.8%]  (FALLTHRU,EXECUTABLE)

Notice the empty `pred', which would indicate to me a block that is
unreachable.

Looking at the tree dump for the rest of the function
(Track::prep_record_enabled(bool, void*)), I see no branches or fall-thrus to
BB 48, so yes... it has become unreachable and should be cleaned up, but the
ICEing code is the one that can't handle empty PHI.


  parent reply	other threads:[~2015-03-02  5:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 10:21 [Bug target/65233] New: [5 Regression] ICE (segfault) on arm-linux-gnueabihf doko at gcc dot gnu.org
2015-02-27 10:32 ` [Bug target/65233] " rguenth at gcc dot gnu.org
2015-02-27 10:41 ` ktkachov at gcc dot gnu.org
2015-02-27 10:53 ` doko at gcc dot gnu.org
2015-02-27 11:46 ` jakub at gcc dot gnu.org
2015-02-27 12:05 ` doko at gcc dot gnu.org
2015-02-27 12:07 ` jakub at gcc dot gnu.org
2015-02-27 20:31 ` aldyh at gcc dot gnu.org
2015-03-01  8:59 ` doko at gcc dot gnu.org
2015-03-01 10:18 ` [Bug target/65233] [5 Regression] ICE (segfault) on arm-linux-gnueabihf and aarch64-linux-gnu doko at gcc dot gnu.org
2015-03-01 10:19 ` doko at gcc dot gnu.org
2015-03-01 15:33 ` aldyh at gcc dot gnu.org
2015-03-01 16:56 ` aldyh at gcc dot gnu.org
2015-03-02  4:38 ` law at redhat dot com
2015-03-02  5:22 ` [Bug middle-end/65233] " aldyh at gcc dot gnu.org
2015-03-02  5:38 ` aldyh at gcc dot gnu.org
2015-03-02  5:49 ` aldyh at gcc dot gnu.org [this message]
2015-03-02  5:50 ` aldyh at gcc dot gnu.org
2015-03-02 21:41 ` law at redhat dot com
2015-03-03 19:33 ` aldyh at gcc dot gnu.org
2015-03-04 13:27 ` rguenth at gcc dot gnu.org
2015-03-05  8:38 ` 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-65233-4-5s8rJW7Hzv@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).