From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com, "Kewen.Lin" <linkw@linux.vnet.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: [PATCH 1/3] rs6000: Remove "wD" from *vsx_extract_<mode>_store
Date: Wed, 5 Oct 2022 19:08:39 +0000 [thread overview]
Message-ID: <19d1d25b1a819a74e01314e6f14b91a847656d4e.1664994970.git.segher@kernel.crashing.org> (raw)
In-Reply-To: <cover.1664994970.git.segher@kernel.crashing.org>
In-Reply-To: <cover.1664994970.git.segher@kernel.crashing.org>
We can use "n" instead of "wD" if we simply test the value of the
integer constant directly.
2022-10-05 Segher Boessenkool <segher@kernel.crashing.org>
* config/rs6000/vsx.md (*vsx_extract_<mode>_store): Use "n" instead of
"wD" constraint.
---
gcc/config/rs6000/vsx.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/gcc/config/rs6000/vsx.md b/gcc/config/rs6000/vsx.md
index e226a93bbe55..79a759b1ccf3 100644
--- a/gcc/config/rs6000/vsx.md
+++ b/gcc/config/rs6000/vsx.md
@@ -3466,8 +3466,9 @@ (define_insn "*vsx_extract_<mode>_store"
[(set (match_operand:<VEC_base> 0 "memory_operand" "=m,Z,wY")
(vec_select:<VEC_base>
(match_operand:VSX_D 1 "register_operand" "d,v,v")
- (parallel [(match_operand:QI 2 "vsx_scalar_64bit" "wD,wD,wD")])))]
- "VECTOR_MEM_VSX_P (<MODE>mode)"
+ (parallel [(match_operand:QI 2 "vsx_scalar_64bit" "n,n,n")])))]
+ "VECTOR_MEM_VSX_P (<MODE>mode)
+ && INTVAL (operands[2]) == (BYTES_BIG_ENDIAN ? 0 : 1)"
"@
stfd%U0%X0 %1,%0
stxsdx %x1,%y0
--
1.8.3.1
next prev parent reply other threads:[~2022-10-05 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 19:08 [PATCH 0/3] rs6000: Get rid of wD Segher Boessenkool
2022-10-05 19:08 ` Segher Boessenkool [this message]
2022-10-05 19:08 ` [PATCH 2/3] rs6000: Rework vsx_extract_<mode> Segher Boessenkool
2022-10-05 19:08 ` [PATCH 3/3] rs6000: Remove the wD constraint 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=19d1d25b1a819a74e01314e6f14b91a847656d4e.1664994970.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.vnet.ibm.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).