From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 3/6] rs6000: Don't use zero_extract in the bswap:HI splitter
Date: Sun, 10 May 2015 16:15:00 -0000 [thread overview]
Message-ID: <fbf9b323d96e5b07c356c3f21bb20d6e859a7891.1431268135.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <cover.1431268134.git.segher@kernel.crashing.org>
In-Reply-To: <cover.1431268134.git.segher@kernel.crashing.org>
The next patch removes the zero_extract insn this splits to. Write
it as (and (lshiftrt ... instead.
Okay for trunk?
Segher
2015-05-10 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/rs6000.md (define_split for bswaphi): Don't use
zero_extract.
---
gcc/config/rs6000/rs6000.md | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/gcc/config/rs6000/rs6000.md b/gcc/config/rs6000/rs6000.md
index acf890c..4bd16ee 100644
--- a/gcc/config/rs6000/rs6000.md
+++ b/gcc/config/rs6000/rs6000.md
@@ -2184,17 +2184,15 @@ (define_insn "bswaphi2_internal"
[(set_attr "length" "4,4,12")
(set_attr "type" "load,store,*")])
-;; We are always BITS_BIG_ENDIAN, so the (const_int 16) below is
-;; correct for -mlittle as well as -mbig.
(define_split
[(set (match_operand:HI 0 "gpc_reg_operand" "")
(bswap:HI (match_operand:HI 1 "gpc_reg_operand" "")))
(clobber (match_operand:SI 2 "gpc_reg_operand" ""))]
"reload_completed"
[(set (match_dup 3)
- (zero_extract:SI (match_dup 4)
- (const_int 8)
- (const_int 16)))
+ (and:SI (lshiftrt:SI (match_dup 4)
+ (const_int 8))
+ (const_int 255)))
(set (match_dup 2)
(and:SI (ashift:SI (match_dup 4)
(const_int 8))
--
1.8.1.4
next prev parent reply other threads:[~2015-05-10 16:15 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 ` Segher Boessenkool [this message]
2015-05-11 15:32 ` [PATCH 3/6] rs6000: Don't use zero_extract in the bswap:HI splitter 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 5/6] rs6000: Don't use gen_rlwinm Segher Boessenkool
2015-05-11 15:30 ` 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 4/6] rs6000: Delete some now-superfluous zero_ext{end,ract} patterns Segher Boessenkool
2015-05-11 15:29 ` 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=fbf9b323d96e5b07c356c3f21bb20d6e859a7891.1431268135.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.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).