public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kyrylo Tkachov <ktkachov@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-178] aarch64: Add vect_concat with zeroes annotation to addp pattern
Date: Sun, 23 Apr 2023 13:41:02 +0000 (GMT)	[thread overview]
Message-ID: <20230423134102.9393D385842C@sourceware.org> (raw)

https://gcc.gnu.org/g:3b13c59c835f92b353ef318398e39907cdeec4fa

commit r14-178-g3b13c59c835f92b353ef318398e39907cdeec4fa
Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Date:   Sun Apr 23 14:40:17 2023 +0100

    aarch64: Add vect_concat with zeroes annotation to addp pattern
    
    Similar to others, the addp pattern can be safely annotated with <vczle><vczbe> to create
    the implicit vec_concat-with-zero variants.
    
    Bootstrapped and tested on aarch64-none-linux-gnu and aarch64_be-none-elf.
    
    gcc/ChangeLog:
    
            PR target/99195
            * config/aarch64/aarch64-simd.md (aarch64_addp<mode>): Rename to...
            (aarch64_addp<mode><vczle><vczbe>): ... This.
    
    gcc/testsuite/ChangeLog:
    
            PR target/99195
            * gcc.target/aarch64/simd/pr99195_1.c: Add testing for vpadd intrinsics.

Diff:
---
 gcc/config/aarch64/aarch64-simd.md                |  2 +-
 gcc/testsuite/gcc.target/aarch64/simd/pr99195_1.c | 17 +++++++++++------
 2 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/gcc/config/aarch64/aarch64-simd.md b/gcc/config/aarch64/aarch64-simd.md
index adcad56cf55..4a1ec71995d 100644
--- a/gcc/config/aarch64/aarch64-simd.md
+++ b/gcc/config/aarch64/aarch64-simd.md
@@ -6767,7 +6767,7 @@
 
 ;; addp
 
-(define_insn "aarch64_addp<mode>"
+(define_insn "aarch64_addp<mode><vczle><vczbe>"
   [(set (match_operand:VDQ_I 0 "register_operand" "=w")
         (unspec:VDQ_I
           [(match_operand:VDQ_I 1 "register_operand" "w")
diff --git a/gcc/testsuite/gcc.target/aarch64/simd/pr99195_1.c b/gcc/testsuite/gcc.target/aarch64/simd/pr99195_1.c
index 3ddd5a37af0..3fe0e53bcd0 100644
--- a/gcc/testsuite/gcc.target/aarch64/simd/pr99195_1.c
+++ b/gcc/testsuite/gcc.target/aarch64/simd/pr99195_1.c
@@ -37,13 +37,18 @@ OPFOUR (T, IS, OS, S, OP2, OP3, OP4, OP5)
 FUNC (T, IS, OS, OP1, S)                \
 OPFIVE (T, IS, OS, S, OP2, OP3, OP4, OP5, OP6)
 
-OPSIX (int8, 8, 16, s8, add, sub, mul, and, orr, eor)
-OPSIX (int16, 4, 8, s16, add, sub, mul, and, orr, eor)
-OPSIX (int32, 2, 4, s32, add, sub, mul, and, orr, eor)
+#define OPSEVEN(T,IS,OS,S,OP1,OP2,OP3,OP4,OP5,OP6,OP7)        \
+FUNC (T, IS, OS, OP1, S)                \
+OPSIX (T, IS, OS, S, OP2, OP3, OP4, OP5, OP6, OP7)
+
+
+OPSEVEN (int8, 8, 16, s8, padd, add, sub, mul, and, orr, eor)
+OPSEVEN (int16, 4, 8, s16, padd, add, sub, mul, and, orr, eor)
+OPSEVEN (int32, 2, 4, s32, padd, add, sub, mul, and, orr, eor)
 
-OPSIX (uint8, 8, 16, u8, add, sub, mul, and, orr, eor)
-OPSIX (uint16, 4, 8, u16, add, sub, mul, and, orr, eor)
-OPSIX (uint32, 2, 4, u32, add, sub, mul, and, orr, eor)
+OPSEVEN (uint8, 8, 16, u8, padd, add, sub, mul, and, orr, eor)
+OPSEVEN (uint16, 4, 8, u16, padd, add, sub, mul, and, orr, eor)
+OPSEVEN (uint32, 2, 4, u32, padd, add, sub, mul, and, orr, eor)
 
 /* { dg-final { scan-assembler-not {\tfmov\t} } }  */
 /* { dg-final { scan-assembler-not {\tmov\t} } }  */

                 reply	other threads:[~2023-04-23 13:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230423134102.9393D385842C@sourceware.org \
    --to=ktkachov@gcc.gnu.org \
    --cc=gcc-cvs@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).