From: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "christophe.lyon@linaro.org" <christophe.lyon@linaro.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Richard Sandiford <Richard.Sandiford@arm.com>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: [PATCH][GCC] aarch64: fix: ls64 tests fail on aarch64_be [PR103729]
Date: Thu, 16 Dec 2021 10:36:21 +0000 [thread overview]
Message-ID: <PAXPR08MB6621C62445C4E8751BBE6659E4779@PAXPR08MB6621.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
Hi,
This patch is sorting issue with LS64 intrinsics tests failing with
AArch64_be targets.
Regtested on aarch64_be_elf and aarch64_elf, no issues.
OK to install?
gcc/ChangeLog:
PR target/PR103729
* config/aarch64/aarch64-simd.md (aarch64_movv8di): Allow big endian
targets to move V8DI.
[-- Attachment #2: rb15153.patch --]
[-- Type: application/octet-stream, Size: 786 bytes --]
diff --git a/gcc/config/aarch64/aarch64-simd.md b/gcc/config/aarch64/aarch64-simd.md
index 9ebf795a624f0183e0333349d0db7a71ba2d17dd..f95a7e1d91c97c9e981d75e71f0b49c02ef748ba 100644
--- a/gcc/config/aarch64/aarch64-simd.md
+++ b/gcc/config/aarch64/aarch64-simd.md
@@ -7265,9 +7265,8 @@ (define_insn "*aarch64_mov<mode>"
(define_insn "*aarch64_movv8di"
[(set (match_operand:V8DI 0 "nonimmediate_operand" "=r,m,r")
(match_operand:V8DI 1 "general_operand" " r,r,m"))]
- "!BYTES_BIG_ENDIAN
- && (register_operand (operands[0], V8DImode)
- || register_operand (operands[1], V8DImode))"
+ "(register_operand (operands[0], V8DImode)
+ || register_operand (operands[1], V8DImode))"
"#"
[(set_attr "type" "multiple,multiple,multiple")
(set_attr "length" "32,16,16")]
next reply other threads:[~2021-12-16 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 10:36 Przemyslaw Wirkus [this message]
2021-12-16 10:45 ` Richard Sandiford
2021-12-16 10:52 ` Przemyslaw Wirkus
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=PAXPR08MB6621C62445C4E8751BBE6659E4779@PAXPR08MB6621.eurprd08.prod.outlook.com \
--to=przemyslaw.wirkus@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=christophe.lyon@linaro.org \
--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).