From: Richard Sandiford <richard.sandiford@arm.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] aarch64: Handle autoinc addresses in ld1rq splitter [PR112906]
Date: Wed, 13 Dec 2023 23:34:17 +0000 [thread overview]
Message-ID: <mpt8r5xy8w6.fsf@arm.com> (raw)
In-Reply-To: <ZXob/Cn/URXcaNVP@arm.com> (Alex Coplan's message of "Wed, 13 Dec 2023 21:02:52 +0000")
Alex Coplan <alex.coplan@arm.com> writes:
> This patch uses the new force_reload_address routine added by the
> previous patch to fix PR112906.
>
> Bootstrapped/regtested on aarch64-linux-gnu, OK for trunk?
OK, thanks, and sorry for the breakage.
Richard
>
> Thanks,
> Alex
>
> gcc/ChangeLog:
>
> PR target/112906
> * config/aarch64/aarch64-sve.md (@aarch64_vec_duplicate_vq<mode>_le):
> Use force_reload_address to reload addresses that aren't suitable for
> ld1rq in the pre-RA splitter.
>
> gcc/testsuite/ChangeLog:
>
> PR target/112906
> * gcc.target/aarch64/sve/acle/general/pr112906.c: New test.
prev parent reply other threads:[~2023-12-13 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 21:02 Alex Coplan
2023-12-13 23:34 ` Richard Sandiford [this message]
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=mpt8r5xy8w6.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=alex.coplan@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).