From: Richard Biener <richard.guenther@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [patch/committed] PR middle-end/65233 make walk-ssa_copies handle empty PHIs
Date: Mon, 02 Mar 2015 08:38:00 -0000 [thread overview]
Message-ID: <CAFiYyc3qQhXgkLB_zgO9fOmqQ0caSpxGTCr6ERy4VJvX4H9jkw@mail.gmail.com> (raw)
In-Reply-To: <54F3F648.8090400@redhat.com>
On Mon, Mar 2, 2015 at 6:34 AM, Aldy Hernandez <aldyh@redhat.com> wrote:
> As I mention in the PR...
>
> What's happening here is that the ipa_polymorphic_call_context constructor
> is calling walk_ssa_copies on a PHI node that has no arguments. This
> happens because finalize_jump_threads eventually removes some PHI arguments
> as it's redirecting some edges, leaving a PHI with no arguments:
>
> SR.33_23 = PHI <>
>
> This should get cleaned up later, but the IPA polymorphic code gets called
> during the actual CFG clean-up, and walk_ssa_copies cannot handle an empty
> PHI.
>
> Approved by Honza.
>
> Fully tested on x86-64 Linux and verified that the patch fixes the ICE on an
> x86-64 Linux cross aarch64-linux-gnu cc1plus.
>
> Committed to mainline.
I think the real issue is that the walking code is executed via fold_stmt when
called with an API that tells you not to walk SSA use-def chains.
Richard.
next prev parent reply other threads:[~2015-03-02 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 5:34 Aldy Hernandez
2015-03-02 8:38 ` Richard Biener [this message]
2015-03-03 20:18 ` Jan Hubicka
2015-03-04 5:27 ` Jeff Law
2015-03-04 12:41 ` Richard Biener
2015-03-04 13:30 ` Richard Biener
2015-03-04 21:22 ` Jan Hubicka
2015-03-05 0:54 ` Jan Hubicka
2015-03-05 8:47 ` Richard Biener
2015-03-05 16:10 ` Jeff Law
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=CAFiYyc3qQhXgkLB_zgO9fOmqQ0caSpxGTCr6ERy4VJvX4H9jkw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).