public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: ramrad01@arm.com, Kyrill Tkachov <kyrylo.tkachov@arm.com>,
	       Jakub Jelinek <jakub@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFC][match.pd] optimize (X & C) == N when C is power of 2
Date: Mon, 27 Jul 2015 16:00:00 -0000	[thread overview]
Message-ID: <55B64E1A.9050400@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1507270931460.19642@zhemvz.fhfr.qr>

On 07/27/2015 01:36 AM, Richard Biener wrote:
>
> I think it also aligns with the idea of pushing back RTL expansion and
> expose some target specifics after another GIMPLE lowering phase.
> I'm also thinking of addressing-mode selection and register promotion.
>
> So at least if we think of that target specific match.pd pass as
> containing all RTL expansion tricks done with TER only then it
> should be quite simple to make it work.
Yea -- I was also thinking it might allow us to clean up some of the 
actual expansion code as well.  It seems promising enough for some 
experimentation.

jeff

  reply	other threads:[~2015-07-27 15:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  8:21 Kyrill Tkachov
2015-07-24  8:36 ` Jakub Jelinek
2015-07-24  8:54   ` Kyrill Tkachov
2015-07-24  9:09     ` Richard Biener
2015-07-24  9:09       ` Kyrill Tkachov
2015-07-24  9:22         ` Ramana Radhakrishnan
2015-07-24  9:16     ` Jakub Jelinek
2015-07-24  9:31       ` Kyrill Tkachov
2015-07-24  9:36         ` Richard Biener
2015-07-24 10:11         ` Jakub Jelinek
2015-07-24 10:25         ` Ramana Radhakrishnan
2015-07-24 18:44           ` Jeff Law
2015-07-27  8:17             ` Richard Biener
2015-07-27 16:00               ` Jeff Law [this message]
2015-07-25  2:37 ` Segher Boessenkool
2015-07-27  8:23   ` Kyrill Tkachov
2015-07-27 15:54     ` Segher Boessenkool

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=55B64E1A.9050400@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=kyrylo.tkachov@arm.com \
    --cc=ramrad01@arm.com \
    --cc=rguenther@suse.de \
    /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).