From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH 2/6] combine: If recog fails, try again with zero_ext{ract,end} simplified
Date: Mon, 11 May 2015 06:18:00 -0000 [thread overview]
Message-ID: <20150511061808.GB2521@gate.crashing.org> (raw)
In-Reply-To: <55502CE6.5010602@redhat.com>
On Sun, May 10, 2015 at 10:15:34PM -0600, Jeff Law wrote:
> > (recog_for_combine): If recog fails, try again with the pattern
> > modified by change_zero_ext; if that still fails, restore the
> > pattern.
> I like it. Attacking the extensions are the most obvious candidates,
> but I wonder if there's others (like the whole "ASHIFT vs MULT" stuff
> that we were recently looking at for ARM).
Yeah, I thought about that as well. But that case, MULT instead of shift,
outside of MEM, is simply non-canonical RTL; and combine created it on
purpose. It just shouldn't.
There certainly will be other cases though; hopefully not overlapping,
I don't want to recog an exponentially expanding number of times ;-)
Segher
next prev parent reply other threads:[~2015-05-11 6:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 16:14 [PATCH 0/6] Getting rid of some zero_ext* patterns Segher Boessenkool
2015-05-10 16:14 ` [PATCH 1/6] combine: undo_to_marker Segher Boessenkool
2015-05-11 4:10 ` Jeff Law
2015-05-10 16:15 ` [PATCH 2/6] combine: If recog fails, try again with zero_ext{ract,end} simplified Segher Boessenkool
2015-05-11 4:15 ` Jeff Law
2015-05-11 6:18 ` Segher Boessenkool [this message]
2015-05-12 8:25 ` Kyrill Tkachov
2015-05-12 11:16 ` Segher Boessenkool
2015-05-10 16:15 ` [PATCH 3/6] rs6000: Don't use zero_extract in the bswap:HI splitter Segher Boessenkool
2015-05-11 15:32 ` David Edelsohn
2015-05-10 16:16 ` [PATCH 4/6] rs6000: Delete some now-superfluous zero_ext{end,ract} patterns Segher Boessenkool
2015-05-11 15:29 ` David Edelsohn
2015-05-10 16:16 ` [PATCH 6/6] rs6000: Clean up the various rlwinm patterns Segher Boessenkool
2015-05-10 18:02 ` Maciej W. Rozycki
2015-05-10 19:45 ` Segher Boessenkool
2015-05-11 18:17 ` Maciej W. Rozycki
2015-05-11 15:31 ` David Edelsohn
2015-05-10 16:16 ` [PATCH 5/6] rs6000: Don't use gen_rlwinm Segher Boessenkool
2015-05-11 15:30 ` David Edelsohn
2015-05-12 14:01 ` [PATCH 0/6] Getting rid of some zero_ext* patterns 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=20150511061808.GB2521@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).