public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111121] AArch64: MOPS memmove operand corruption
Date: Fri, 29 Sep 2023 12:14:55 +0000 [thread overview]
Message-ID: <bug-111121-4-mF1xFEo9MQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111121-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111121
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Wilco Dijkstra
<wilco@gcc.gnu.org>:
https://gcc.gnu.org/g:c534a9b198caa3807bcc592a3c5bac3f971417f7
commit r13-7921-gc534a9b198caa3807bcc592a3c5bac3f971417f7
Author: Wilco Dijkstra <wilco.dijkstra@arm.com>
Date: Tue Sep 26 16:42:45 2023 +0100
AArch64: Fix memmove operand corruption [PR111121]
A MOPS memmove may corrupt registers since there is no copy of the input
operands to temporary registers. Fix this by calling
aarch64_expand_cpymem_mops.
Reviewed-by: Richard Sandiford <richard.sandiford@arm.com>
gcc/ChangeLog/
PR target/111121
* config/aarch64/aarch64.md (aarch64_movmemdi): Add new expander.
(movmemdi): Call aarch64_expand_cpymem_mops for correct expansion.
* config/aarch64/aarch64.cc (aarch64_expand_cpymem_mops): Add
support
for memmove.
* config/aarch64/aarch64-protos.h (aarch64_expand_cpymem_mops): Add
new
function.
gcc/testsuite/ChangeLog/
PR target/111121
* gcc.target/aarch64/mops_4.c: Add memmove testcases.
(cherry picked from commit d8b56c95782aeeee79ec40932ca88d00fd9f2ee2)
next prev parent reply other threads:[~2023-09-29 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:25 [Bug target/111121] New: " wilco at gcc dot gnu.org
2023-08-23 14:26 ` [Bug target/111121] " wilco at gcc dot gnu.org
2023-08-23 14:26 ` wilco at gcc dot gnu.org
2023-08-23 17:34 ` pinskia at gcc dot gnu.org
2023-08-24 6:44 ` rguenth at gcc dot gnu.org
2023-09-28 15:34 ` cvs-commit at gcc dot gnu.org
2023-09-29 12:14 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-29 12:15 ` cvs-commit at gcc dot gnu.org
2023-09-29 12:25 ` wilco at gcc dot gnu.org
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=bug-111121-4-mF1xFEo9MQ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).