public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jeff Law <law@redhat.com>, Aldy Hernandez <aldyh@redhat.com>,
	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: Thu, 05 Mar 2015 00:54:00 -0000	[thread overview]
Message-ID: <20150305005444.GD86051@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc0k5pkR8ju+VM1G6FNvg2xkjRwPEu6XtZuqy-uENc3GYQ@mail.gmail.com>

> >
> > It gets passed the valueize callback now which returns NULL_TREE for
> > SSA names we can't follow.
> 
> Btw, for match-and-simplify I had to use that as default for fold_stmt
> _exactly_ because of the call to fold_stmt from replace_uses_by
> via merge-blocks from cfgcleanup.  This is because replace-uses-by
> doesn't have all uses replaced before it folds the stmt!
> 
> We also have the "weaker" in-place flag.
> 
> 2015-03-04  Richard Biener  <rguenther@suse.de>
> 
>         PR middle-end/65233
>         * ipa-polymorphic-call.c: Include tree-ssa-operands.h and
>         tree-into-ssa.h.
>         (walk_ssa_copies): Revert last chage.  Instead do not walk
>         SSA names registered for SSA update.

Maybe include the patch?  It should not be problem to make the function
to valuelize everything it looks into.

Honza

  parent reply	other threads:[~2015-03-05  0:54 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
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 [this message]
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=20150305005444.GD86051@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=richard.guenther@gmail.com \
    /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).