From: KuanLin Chen <best124612@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] RISC-V:Raname UNSPEC_CLMUL in vector-crypto.md
Date: Fri, 19 Jan 2024 10:30:18 +0800 [thread overview]
Message-ID: <CA+jpiRcdA4w=cdYBj3QdSMKtjU22R+2vOdUCZGE26Jz=c=p9Dw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 209 bytes --]
UNSPEC_CLMUL is defined to define_c_enum in riscv.md, so
it shouldn't be redefined to define_int_iterator again.
*gcc/ChangeLog:*
* config/riscv/vector-crypto.md (UNSPEC_CLMUL): Rename to UNSPEC_CLMUL_VC.
[-- Attachment #2: 0001-RISC-V-Raname-UNSPEC_CLMUL-in-vector-crypto.md.patch --]
[-- Type: application/octet-stream, Size: 2802 bytes --]
From 99faef21e88b6c5f3fa5ccca08c1a57e3b792a55 Mon Sep 17 00:00:00 2001
From: Kuan-Lin Chen <rufus@andestech.com>
Date: Fri, 19 Jan 2024 09:53:27 +0800
Subject: [PATCH] RISC-V: Raname UNSPEC_CLMUL in vector-crypto.md.
UNSPEC_CLMUL is defined to define_c_enum in riscv.md, so
it shouldn't be redefined to define_int_iterator again.
---
gcc/config/riscv/vector-crypto.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/gcc/config/riscv/vector-crypto.md b/gcc/config/riscv/vector-crypto.md
index 9625014e45e..3b270b74b70 100755
--- a/gcc/config/riscv/vector-crypto.md
+++ b/gcc/config/riscv/vector-crypto.md
@@ -81,7 +81,7 @@
(define_int_iterator UNSPEC_VRBB8 [UNSPEC_VBREV UNSPEC_VBREV8 UNSPEC_VREV8])
-(define_int_iterator UNSPEC_CLMUL [UNSPEC_VCLMUL UNSPEC_VCLMULH])
+(define_int_iterator UNSPEC_CLMUL_VC [UNSPEC_VCLMUL UNSPEC_VCLMULH])
(define_int_iterator UNSPEC_CRYPTO_VV [UNSPEC_VGMUL UNSPEC_VAESEFVV UNSPEC_VAESEMVV
UNSPEC_VAESDFVV UNSPEC_VAESDMVV UNSPEC_VAESEFVS
@@ -377,7 +377,7 @@
(reg:SI VTYPE_REGNUM)] UNSPEC_VPREDICATE)
(unspec:VI_D
[(match_operand:VI_D 3 "register_operand" "vr, vr,vr, vr")
- (match_operand:VI_D 4 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL)
+ (match_operand:VI_D 4 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL_VC)
(match_operand:VI_D 2 "vector_merge_operand" "vu, vu, 0, 0")))]
"TARGET_ZVBC"
"vclmul<h>.vv\t%0,%3,%4%p1"
@@ -399,7 +399,7 @@
(unspec:VI_D
[(vec_duplicate:VI_D
(match_operand:<VEL> 4 "register_operand"))
- (match_operand:VI_D 3 "register_operand")]UNSPEC_CLMUL)
+ (match_operand:VI_D 3 "register_operand")]UNSPEC_CLMUL_VC)
(match_operand:VI_D 2 "vector_merge_operand")))]
"TARGET_ZVBC"
{
@@ -432,7 +432,7 @@
(unspec:VI_D
[(vec_duplicate:VI_D
(match_operand:<VEL> 4 "reg_or_0_operand" "rJ, rJ,rJ, rJ"))
- (match_operand:VI_D 3 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL)
+ (match_operand:VI_D 3 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL_VC)
(match_operand:VI_D 2 "vector_merge_operand" "vu, vu, 0, 0")))]
"TARGET_ZVBC"
"vclmul<h>.vx\t%0,%3,%4%p1"
@@ -454,7 +454,7 @@
[(vec_duplicate:VI_D
(sign_extend:<VEL>
(match_operand:<VSUBEL> 4 "reg_or_0_operand" " rJ, rJ,rJ, rJ")))
- (match_operand:VI_D 3 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL)
+ (match_operand:VI_D 3 "register_operand" "vr, vr,vr, vr")]UNSPEC_CLMUL_VC)
(match_operand:VI_D 2 "vector_merge_operand" "vu, vu, 0, 0")))]
"TARGET_ZVBC"
"vclmul<h>.vx\t%0,%3,%4%p1"
--
2.42.0.345.gaab89be2eb.dirty
next reply other threads:[~2024-01-19 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 2:30 KuanLin Chen [this message]
2024-01-19 2:41 ` Kito Cheng
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='CA+jpiRcdA4w=cdYBj3QdSMKtjU22R+2vOdUCZGE26Jz=c=p9Dw@mail.gmail.com' \
--to=best124612@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).