From: Richard Sandiford <richard.sandiford@arm.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: gcc-patches@gcc.gnu.org,
Richard Earnshaw <richard.earnshaw@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: [PATCH 0/3] aarch64: ls64 builtin fixes [PR110100,PR110132]
Date: Wed, 07 Jun 2023 16:51:37 +0100 [thread overview]
Message-ID: <mptcz27p8xi.fsf@arm.com> (raw)
In-Reply-To: <ZICNVVJIbXMgHgED@arm.com> (Alex Coplan's message of "Wed, 7 Jun 2023 14:59:49 +0100")
Alex Coplan <alex.coplan@arm.com> writes:
> Hi,
>
> This patch series fixes various defects with the FEAT_LS64 ACLE
> implementation in the AArch64 backend.
>
> The series is organised as follows:
>
> - Patch 1/3 fixes whitespace errors in the existing code.
> - Patch 2/3 fixes PR110100 where we generate wrong code for the st64b
> builtin.
> - Patch 3/3 fixes PR110132, allowing the compiler to define the ACLE builtins
> directly, and also makes the builtins work under LTO.
>
> Bootstrapped/regtested as a series on aarch64-linux-gnu. OK for trunk
> and backports back to GCC 12?
Yeah, OK for trunk and branches. Thanks for fixing this.
Richard
prev parent reply other threads:[~2023-06-07 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 13:59 Alex Coplan
2023-06-07 15:51 ` 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=mptcz27p8xi.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=richard.earnshaw@arm.com \
/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).