From: Alex Coplan <alex.coplan@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw <richard.earnshaw@arm.com>,
Richard Sandiford <richard.sandiford@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Subject: [PATCH 0/3] aarch64: ls64 builtin fixes [PR110100,PR110132]
Date: Wed, 7 Jun 2023 14:59:49 +0100 [thread overview]
Message-ID: <ZICNVVJIbXMgHgED@arm.com> (raw)
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?
Thanks,
Alex
Alex Coplan (3):
aarch64: Fix whitespace in ls64 builtin implementation [PR110100]
aarch64: Fix wrong code with st64b builtin [PR110100]
aarch64: Allow compiler to define ls64 builtins [PR110132]
gcc/config/aarch64/aarch64-builtins.cc | 88 +++++++++++--------
gcc/config/aarch64/aarch64.md | 24 ++---
gcc/config/aarch64/arm_acle.h | 33 -------
.../g++.target/aarch64/acle/acle.exp | 35 ++++++++
gcc/testsuite/g++.target/aarch64/acle/ls64.C | 10 +++
.../g++.target/aarch64/acle/ls64_lto.C | 10 +++
.../gcc.target/aarch64/acle/ls64_lto.c | 10 +++
.../gcc.target/aarch64/acle/pr110100.c | 7 ++
.../gcc.target/aarch64/acle/pr110132.c | 15 ++++
gcc/testsuite/lib/target-supports.exp | 2 +-
10 files changed, 151 insertions(+), 83 deletions(-)
create mode 100644 gcc/testsuite/g++.target/aarch64/acle/acle.exp
create mode 100644 gcc/testsuite/g++.target/aarch64/acle/ls64.C
create mode 100644 gcc/testsuite/g++.target/aarch64/acle/ls64_lto.C
create mode 100644 gcc/testsuite/gcc.target/aarch64/acle/ls64_lto.c
create mode 100644 gcc/testsuite/gcc.target/aarch64/acle/pr110100.c
create mode 100644 gcc/testsuite/gcc.target/aarch64/acle/pr110132.c
next reply other threads:[~2023-06-07 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 13:59 Alex Coplan [this message]
2023-06-07 15:51 ` Richard Sandiford
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=ZICNVVJIbXMgHgED@arm.com \
--to=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@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).