From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: [aarch64] Use wzr/xzr for assigning vector element to 0
Date: Tue, 17 Jan 2023 16:16:45 +0530 [thread overview]
Message-ID: <CAAgBjM=J8Vye=RPBw1sWQnUzxfC1C2UPT_vc+_jmXOeYJG-YGQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
Hi Richard,
For the following (contrived) test:
void foo(int32x4_t v)
{
v[3] = 0;
return v;
}
-O2 code-gen:
foo:
fmov s1, wzr
ins v0.s[3], v1.s[0]
ret
I suppose we can instead emit the following code-gen ?
foo:
ins v0.s[3], wzr
ret
combine produces:
Failed to match this instruction:
(set (reg:V4SI 95 [ v ])
(vec_merge:V4SI (const_vector:V4SI [
(const_int 0 [0]) repeated x4
])
(reg:V4SI 97)
(const_int 8 [0x8])))
So, I wrote the following pattern to match the above insn:
(define_insn "aarch64_simd_vec_set_zero<mode>"
[(set (match_operand:VALL_F16 0 "register_operand" "=w")
(vec_merge:VALL_F16
(match_operand:VALL_F16 1 "const_dup0_operand" "w")
(match_operand:VALL_F16 3 "register_operand" "0")
(match_operand:SI 2 "immediate_operand" "i")))]
"TARGET_SIMD"
{
int elt = ENDIAN_LANE_N (<nunits>, exact_log2 (INTVAL (operands[2])));
operands[2] = GEN_INT ((HOST_WIDE_INT) 1 << elt);
return "ins\\t%0.<Vetype>[%p2], wzr";
}
)
which now matches the above insn produced by combine.
However, in reload dump, it creates a new insn for assigning
register to (const_vector (const_int 0)),
which results in:
(insn 19 8 13 2 (set (reg:V4SI 33 v1 [99])
(const_vector:V4SI [
(const_int 0 [0]) repeated x4
])) "wzr-test.c":8:1 1269 {*aarch64_simd_movv4si}
(nil))
(insn 13 19 14 2 (set (reg/i:V4SI 32 v0)
(vec_merge:V4SI (reg:V4SI 33 v1 [99])
(reg:V4SI 32 v0 [97])
(const_int 8 [0x8]))) "wzr-test.c":8:1 1808
{aarch64_simd_vec_set_zerov4si}
(nil))
and eventually the code-gen:
foo:
movi v1.4s, 0
ins v0.s[3], wzr
ret
To get rid of redundant assignment of 0 to v1, I tried to split the
above pattern
as in the attached patch. This works to emit code-gen:
foo:
ins v0.s[3], wzr
ret
However, I am not sure if this is the right approach. Could you suggest,
if it'd be possible to get rid of UNSPEC_SETZERO in the patch ?
Thanks,
Prathamesh
[-- Attachment #2: gnu-811-4.txt --]
[-- Type: text/plain, Size: 2664 bytes --]
diff --git a/gcc/config/aarch64/aarch64-simd.md b/gcc/config/aarch64/aarch64-simd.md
index 104088f67d2..5130f46c0da 100644
--- a/gcc/config/aarch64/aarch64-simd.md
+++ b/gcc/config/aarch64/aarch64-simd.md
@@ -1083,6 +1083,39 @@
[(set_attr "type" "neon_ins<q>, neon_from_gp<q>, neon_load1_one_lane<q>")]
)
+(define_insn "aarch64_simd_set_zero<mode>"
+ [(set (match_operand:VALL_F16 0 "register_operand" "=w")
+ (unspec:VALL_F16 [(match_operand:VALL_F16 1 "register_operand" "0")
+ (match_operand:SI 2 "immediate_operand" "i")]
+ UNSPEC_SETZERO))]
+ "TARGET_SIMD"
+ {
+ if (GET_MODE_INNER (<MODE>mode) == DImode)
+ return "ins\\t%0.<Vetype>[%p2], xzr";
+ return "ins\\t%0.<Vetype>[%p2], wzr";
+ }
+ [(set_attr "type" "neon_ins<q>")]
+)
+
+(define_insn_and_split "aarch64_simd_vec_set_zero<mode>"
+ [(set (match_operand:VALL_F16 0 "register_operand" "=w")
+ (vec_merge:VALL_F16
+ (match_operand:VALL_F16 1 "const_dup0_operand" "w")
+ (match_operand:VALL_F16 3 "register_operand" "0")
+ (match_operand:SI 2 "immediate_operand" "i")))]
+ "TARGET_SIMD"
+ "#"
+ "&& 1"
+ [(const_int 0)]
+ {
+ int elt = ENDIAN_LANE_N (<nunits>, exact_log2 (INTVAL (operands[2])));
+ operands[2] = GEN_INT ((HOST_WIDE_INT) 1 << elt);
+ emit_insn (gen_aarch64_simd_set_zero<mode> (operands[0], operands[3], operands[2]));
+ DONE;
+ }
+ [(set_attr "type" "neon_ins<q>")]
+)
+
(define_insn "@aarch64_simd_vec_copy_lane<mode>"
[(set (match_operand:VALL_F16 0 "register_operand" "=w")
(vec_merge:VALL_F16
diff --git a/gcc/config/aarch64/iterators.md b/gcc/config/aarch64/iterators.md
index 5b26443e5b6..8064841ebb4 100644
--- a/gcc/config/aarch64/iterators.md
+++ b/gcc/config/aarch64/iterators.md
@@ -839,6 +839,7 @@
UNSPEC_FCMUL_CONJ ; Used in aarch64-simd.md.
UNSPEC_FCMLA_CONJ ; Used in aarch64-simd.md.
UNSPEC_FCMLA180_CONJ ; Used in aarch64-simd.md.
+ UNSPEC_SETZERO ; Used in aarch64-simd.md.
UNSPEC_ASRD ; Used in aarch64-sve.md.
UNSPEC_ADCLB ; Used in aarch64-sve2.md.
UNSPEC_ADCLT ; Used in aarch64-sve2.md.
diff --git a/gcc/config/aarch64/predicates.md b/gcc/config/aarch64/predicates.md
index ff7f73d3f30..901fa1bd7f9 100644
--- a/gcc/config/aarch64/predicates.md
+++ b/gcc/config/aarch64/predicates.md
@@ -49,6 +49,13 @@
return CONST_INT_P (op) && IN_RANGE (INTVAL (op), 1, 3);
})
+(define_predicate "const_dup0_operand"
+ (match_code "const_vector")
+{
+ op = unwrap_const_vec_duplicate (op);
+ return CONST_INT_P (op) && rtx_equal_p (op, const0_rtx);
+})
+
(define_predicate "subreg_lowpart_operator"
(ior (match_code "truncate")
(and (match_code "subreg")
next reply other threads:[~2023-01-17 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 10:46 Prathamesh Kulkarni [this message]
2023-01-17 12:59 ` Richard Sandiford
2023-01-18 10:47 ` Prathamesh Kulkarni
2023-01-18 14:29 ` Richard Sandiford
2023-01-19 12:07 ` Prathamesh Kulkarni
2023-01-23 16:56 ` Richard Sandiford
2023-01-25 11:56 ` Prathamesh Kulkarni
2023-01-31 6:21 ` Richard Sandiford
2023-04-19 8:42 ` Prathamesh Kulkarni
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='CAAgBjM=J8Vye=RPBw1sWQnUzxfC1C2UPT_vc+_jmXOeYJG-YGQ@mail.gmail.com' \
--to=prathamesh.kulkarni@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).