public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] riscv: thead: Fix mode attribute for extension patterns
Date: Mon, 11 Sep 2023 13:38:40 +0000 (GMT) [thread overview]
Message-ID: <20230911133840.41F013858002@sourceware.org> (raw)
https://gcc.gnu.org/g:4408e05b05aa88adf0acc3f5f6bef4d21766c72a
commit 4408e05b05aa88adf0acc3f5f6bef4d21766c72a
Author: Christoph Müllner <christoph.muellner@vrull.eu>
Date: Fri Sep 8 08:03:23 2023 +0200
riscv: thead: Fix mode attribute for extension patterns
The mode attribute of an extension pattern is usually set to the target type.
Let's follow this convention consistently for xtheadbb.
Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
gcc/ChangeLog:
* config/riscv/thead.md: Use more appropriate mode attributes
for extensions.
(cherry picked from commit 0e25761b373f075a41d43b9462366a653dbf1121)
Diff:
---
gcc/config/riscv/thead.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/config/riscv/thead.md b/gcc/config/riscv/thead.md
index 29f98dec3a8a..c6bd6887f9f7 100644
--- a/gcc/config/riscv/thead.md
+++ b/gcc/config/riscv/thead.md
@@ -90,7 +90,7 @@
th.extu\t%0,%1,31,0
lwu\t%0,%1"
[(set_attr "type" "bitmanip,load")
- (set_attr "mode" "SI")])
+ (set_attr "mode" "DI")])
(define_insn "*zero_extendhi<GPR:mode>2_th_extu"
[(set (match_operand:GPR 0 "register_operand" "=r,r")
@@ -100,7 +100,7 @@
th.extu\t%0,%1,15,0
lhu\t%0,%1"
[(set_attr "type" "bitmanip,load")
- (set_attr "mode" "HI")])
+ (set_attr "mode" "<GPR:MODE>")])
(define_insn "*th_clz<mode>2"
[(set (match_operand:X 0 "register_operand" "=r")
reply other threads:[~2023-09-11 13:38 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=20230911133840.41F013858002@sourceware.org \
--to=law@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).