From: David Edelsohn <dje.gcc@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 4/6] rs6000: Delete some now-superfluous zero_ext{end,ract} patterns
Date: Mon, 11 May 2015 15:29:00 -0000 [thread overview]
Message-ID: <CAGWvnyk95o7uBtzNheCrK6DWzee+EpSnffdOz7jUdMzjHzLZyA@mail.gmail.com> (raw)
In-Reply-To: <6f14d7233a743b19ad370a9723430344264cbf2d.1431268135.git.segher@kernel.crashing.org>
On Sun, May 10, 2015 at 12:13 PM, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
> After the change to combine, we no longer need all the special-case
> patterns.
>
> Tested on powerpc64-linux, as usual. As mentioned with the combine
> patch, there are no differences to generated code in cc1.
>
> This does not delete DImode lshiftrt patterns, because those do not
> exist (yet).
>
> Is this okay for trunk?
>
>
> Segher
>
> [ Save the planet! Delete 11% of your machine descriptions! ]
>
>
> 2015-05-10 Segher Boessenkool <segher@kernel.crashing.org>
>
> * config/rs6000/rs6000.md (extzv): FAIL for SImode.
> (extzvsi_internal, *extzvsi_internal1, *extzvsi_internal2,
> *rotlsi3_internal7le, *rotlsi3_internal7be, *rotlsi3_internal8le,
> *rotlsi3_internal8be, *rotlsi3_internal9le, *rotlsi3_internal9be,
> *rotlsi3_internal10le, *rotlsi3_internal10be, *rotlsi3_internal11le,
> *rotlsi3_internal11be, *rotlsi3_internal12le, *rotlsi3_internal12be,
> *lshiftrt_internal1le, *lshiftrt_internal1be, *lshiftrt_internal2le,
> *lshiftrt_internal2be, *lshiftrt_internal3le, *lshiftrt_internal3be,
> *lshiftrt_internal4le, *lshiftrt_internal4be, *lshiftrt_internal5le,
> *lshiftrt_internal5be, *lshiftrt_internal5le, *lshiftrt_internal5be,
> *rotldi3_internal7le, *rotldi3_internal7be, *rotldi3_internal8le,
> *rotldi3_internal8be, *rotldi3_internal9le, *rotldi3_internal9be,
> *rotldi3_internal10le, *rotldi3_internal10be, *rotldi3_internal11le,
> *rotldi3_internal11be, *rotldi3_internal12le, *rotldi3_internal12be,
> *rotldi3_internal13le, *rotldi3_internal13be, *rotldi3_internal14le,
> *rotldi3_internal14be, *rotldi3_internal15le, *rotldi3_internal15be,
> and 30 corresponding splitters): Delete.
Okay.
Thanks, David
next prev parent reply other threads:[~2015-05-11 15:29 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 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: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
2015-05-12 8:25 ` Kyrill Tkachov
2015-05-12 11:16 ` Segher Boessenkool
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 4/6] rs6000: Delete some now-superfluous zero_ext{end,ract} patterns Segher Boessenkool
2015-05-11 15:29 ` David Edelsohn [this message]
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=CAGWvnyk95o7uBtzNheCrK6DWzee+EpSnffdOz7jUdMzjHzLZyA@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).