public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PING][PATCH, 1/2] Merge rewrite_virtuals_into_loop_closed_ssa from gomp4 branch
Date: Wed, 08 Jul 2015 13:31:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1507081529000.9923@zhemvz.fhfr.qr> (raw)
In-Reply-To: <559BF70D.9050201@mentor.com>

On Tue, 7 Jul 2015, Tom de Vries wrote:

> On 06/07/15 15:44, Richard Biener wrote:
> > Please add this to tree-cfg.[ch] instead, there are multiple places
> > in GCC that would benefit from it
> 
> Done.
> 
> A lot of calls to mark_virtual_phi_result_for_renaming look like they could be
> rewritten using get_virtual_phi.

Yeah - patches to make use of get_virtual_phi are pre-approved if they
look obvious enough.

Richard.

  parent reply	other threads:[~2015-07-08 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  7:44 [PATCH, " Tom de Vries
2015-07-06 10:13 ` [PING][PATCH, " Tom de Vries
2015-07-06 13:44   ` Richard Biener
2015-07-07 15:58     ` Tom de Vries
2015-07-08 13:04       ` [gomp4, committed] Add rewrite_virtuals_into_loop_closed_ssa Tom de Vries
2015-07-08 13:31       ` Richard Biener [this message]
2015-07-09  3:33       ` [PING][PATCH, 1/2] Merge rewrite_virtuals_into_loop_closed_ssa from gomp4 branch Jeff Law
2015-07-09  9:19         ` Tom de Vries
2015-07-09 16:49           ` Jeff Law
2015-07-09 10:59       ` Tom de Vries
2015-07-09 11:04         ` Richard Biener
2015-07-20 16:13           ` Tom de Vries
2015-07-23 13:52             ` Richard Biener
2015-08-31 10:55               ` Tom de Vries
2015-08-31 12:42                 ` Richard Biener

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=alpine.LSU.2.11.1507081529000.9923@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@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).