From: Christophe Lyon <christophe.lyon@arm.com>
To: <gcc-patches@gcc.gnu.org>
Cc: Christophe Lyon <christophe.lyon@arm.com>
Subject: [PATCH] arm: [MVE] Add missing length=8 attribute
Date: Wed, 1 Feb 2023 10:46:50 +0100 [thread overview]
Message-ID: <20230201094650.65755-2-christophe.lyon@arm.com> (raw)
In-Reply-To: <20230201094650.65755-1-christophe.lyon@arm.com>
I have noticed that the "length" "8" attribute is missing in a few
patterns in mve.md.
gcc/
* config/arm/mve.md (mve_vabavq_p_<supf><mode>): Add length
attribute.
(mve_vqshluq_m_n_s<mode>): Likewise.
(mve_vshlq_m_<supf><mode>): Likewise.
(mve_vsriq_m_n_<supf><mode>): Likewise.
(mve_vsubq_m_<supf><mode>): Likewise.
---
gcc/config/arm/mve.md | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/gcc/config/arm/mve.md b/gcc/config/arm/mve.md
index 555ad1b66c8..8a05371e14a 100644
--- a/gcc/config/arm/mve.md
+++ b/gcc/config/arm/mve.md
@@ -4979,7 +4979,7 @@ (define_insn "mve_vabavq_p_<supf><mode>"
"TARGET_HAVE_MVE"
"vpst\;vabavt.<supf>%#<V_sz_elem>\t%0, %q2, %q3"
[(set_attr "type" "mve_move")
-])
+ (set_attr "length" "8")])
;;
;; [vqshluq_m_n_s])
@@ -4995,7 +4995,8 @@ (define_insn "mve_vqshluq_m_n_s<mode>"
]
"TARGET_HAVE_MVE"
"vpst\n\tvqshlut.s%#<V_sz_elem>\t%q0, %q2, %3"
- [(set_attr "type" "mve_move")])
+ [(set_attr "type" "mve_move")
+ (set_attr "length" "8")])
;;
;; [vshlq_m_s, vshlq_m_u])
@@ -5011,7 +5012,8 @@ (define_insn "mve_vshlq_m_<supf><mode>"
]
"TARGET_HAVE_MVE"
"vpst\;vshlt.<supf>%#<V_sz_elem>\t%q0, %q2, %q3"
- [(set_attr "type" "mve_move")])
+ [(set_attr "type" "mve_move")
+ (set_attr "length" "8")])
;;
;; [vsriq_m_n_s, vsriq_m_n_u])
@@ -5027,7 +5029,8 @@ (define_insn "mve_vsriq_m_n_<supf><mode>"
]
"TARGET_HAVE_MVE"
"vpst\;vsrit.%#<V_sz_elem>\t%q0, %q2, %3"
- [(set_attr "type" "mve_move")])
+ [(set_attr "type" "mve_move")
+ (set_attr "length" "8")])
;;
;; [vsubq_m_u, vsubq_m_s])
@@ -5043,7 +5046,8 @@ (define_insn "mve_vsubq_m_<supf><mode>"
]
"TARGET_HAVE_MVE"
"vpst\;vsubt.i%#<V_sz_elem>\t%q0, %q2, %q3"
- [(set_attr "type" "mve_move")])
+ [(set_attr "type" "mve_move")
+ (set_attr "length" "8")])
;;
;; [vcvtq_m_n_to_f_u, vcvtq_m_n_to_f_s])
--
2.34.1
next prev parent reply other threads:[~2023-02-01 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 9:46 [PATCH] arm: Fix warning in libgcc/config/arm/pr-support.c Christophe Lyon
2023-02-01 9:46 ` Christophe Lyon [this message]
2023-02-03 15:35 ` [PATCH] arm: [MVE] Add missing length=8 attribute Richard Earnshaw
2023-02-03 15:34 ` [PATCH] arm: Fix warning in libgcc/config/arm/pr-support.c Richard Earnshaw
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=20230201094650.65755-2-christophe.lyon@arm.com \
--to=christophe.lyon@arm.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).