public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: combine permutations in gimple
Date: Mon, 13 Aug 2012 15:43:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1208131732430.3258@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <alpine.DEB.2.02.1208131523240.3258@laptop-mg.saclay.inria.fr>

On Mon, 13 Aug 2012, Marc Glisse wrote:

> On Mon, 13 Aug 2012, Richard Guenther wrote:
>
>> If your new predicate would match more places (can you do a quick search?)
>
> You mean: if there are more optimizations that either already check for 
> double use in the same statement, or could benefit from doing so? I'll take a 
> look.

I couldn't find anything obvious (not that I understood a significant 
percentage of what I saw...).

Note that the comments are efficient since the only current use of 
num_imm_uses is in a debug printf call.


I'll give it a few more days for the conversation to settle, so I know 
what I should do between:
- the barely modified patch you accepted,
- the check asked by Jakub,
- the restriction to identity that prevents any regression (well...),
- something else?

-- 
Marc Glisse

  reply	other threads:[~2012-08-13 15:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 21:40 Marc Glisse
2012-08-10 21:48 ` Marc Glisse
2012-08-11 12:25 ` Marc Glisse
2012-08-13 12:23   ` Richard Guenther
2012-08-13 13:04     ` Marc Glisse
2012-08-13 13:10       ` Richard Guenther
2012-08-13 13:29         ` Marc Glisse
2012-08-13 15:43           ` Marc Glisse [this message]
2012-08-15 11:22             ` Marc Glisse
2012-08-15 11:46               ` Richard Guenther
2012-08-15 12:09                 ` Jakub Jelinek
2012-08-15 12:15                   ` Richard Guenther
2012-08-15 12:34                     ` Jakub Jelinek
2012-08-15 12:37                       ` Richard Guenther
2012-08-15 12:59                         ` Jakub Jelinek
2012-08-15 13:09                           ` Richard Guenther
2012-08-15 12:21                   ` Ramana Radhakrishnan
2012-08-18 10:00               ` Marc Glisse
2012-08-20 11:35                 ` Richard Guenther
2012-08-13 13:12       ` Ramana Radhakrishnan
2012-08-13 13:13         ` Richard Guenther
2012-08-13 13:21           ` Marc Glisse
2012-08-13 14:05             ` Ramana Radhakrishnan
2012-08-13 14:29               ` Marc Glisse
2012-08-15 11:57                 ` Ramana Radhakrishnan
2012-08-15 12:06                   ` Richard Guenther
2012-08-17  3:03                     ` Hans-Peter Nilsson
2012-08-13 13:27           ` Jakub Jelinek
2012-08-13 13:45             ` Marc Glisse
2012-08-13 13:59               ` Jakub Jelinek
2012-08-13 14:12                 ` Ramana Radhakrishnan
2012-08-13 14:43                   ` Richard Guenther

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.DEB.2.02.1208131732430.3258@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --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).