public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [PR40457] [arm] expand SI-aligned movdi into pair of movsi
Date: Thu, 1 Dec 2022 07:40:08 +0000 (GMT) [thread overview]
Message-ID: <20221201074008.5D1D43858289@sourceware.org> (raw)
https://gcc.gnu.org/g:cec475ae63c3659241dbd5c474990b5103148f86
commit cec475ae63c3659241dbd5c474990b5103148f86
Author: Alexandre Oliva <oliva@adacore.com>
Date: Thu Dec 1 04:38:48 2022 -0300
[PR40457] [arm] expand SI-aligned movdi into pair of movsi
When expanding a misaligned DImode move, emit aligned SImode moves if
the parts are sufficiently aligned. This enables neighboring stores
to be peephole-combined into stm, as expected by the PR40457 testcase,
even after SLP vectorizes the originally aligned SImode stores into a
misaligned DImode store.
for gcc/ChangeLog
PR target/40457
* config/arm/arm.md (movmisaligndi): Prefer aligned SImode
moves.
Change-Id: Ib91440e12e6ff424e3e7359874bf38c2779887a0
TN: VB12-014
Diff:
---
gcc/config/arm/arm.md | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/gcc/config/arm/arm.md b/gcc/config/arm/arm.md
index 69bf343fb0e..a9eb0299aa7 100644
--- a/gcc/config/arm/arm.md
+++ b/gcc/config/arm/arm.md
@@ -12783,8 +12783,16 @@
rtx hi_op0 = gen_highpart_mode (SImode, DImode, operands[0]);
rtx hi_op1 = gen_highpart_mode (SImode, DImode, operands[1]);
- emit_insn (gen_movmisalignsi (lo_op0, lo_op1));
- emit_insn (gen_movmisalignsi (hi_op0, hi_op1));
+ if (aligned_operand (lo_op0, SImode) && aligned_operand (lo_op1, SImode))
+ {
+ emit_move_insn (lo_op0, lo_op1);
+ emit_move_insn (hi_op0, hi_op1);
+ }
+ else
+ {
+ emit_insn (gen_movmisalignsi (lo_op0, lo_op1));
+ emit_insn (gen_movmisalignsi (hi_op0, hi_op1));
+ }
DONE;
})
next reply other threads:[~2022-12-01 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 7:40 Alexandre Oliva [this message]
2022-12-03 7:33 Alexandre Oliva
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=20221201074008.5D1D43858289@sourceware.org \
--to=aoliva@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).