From: Andrew Carlotti <andrew.carlotti@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Biener <richard.guenther@gmail.com>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: [PATCH v3 0/5] target_version and aarch64 function multiversioning
Date: Wed, 6 Dec 2023 12:43:04 +0000 [thread overview]
Message-ID: <4cdd7089-edd4-96b9-5c0e-120d5357f01b@e124511.cambridge.arm.com> (raw)
This series adds support for function multiversioning on aarch64.
Patches 1-3 are already approved, with just one minor change from the previous
version of patch 1 suggested by Richard Sandiford.
Patches 4-5 are updated based on Richard's reviews. The only major change is
replacing the EXPANDED_CLONES_ATTRIBUTE target hook with the
TARGET_HAS_FMV_TARGET_ATTRIBUTE macro. I've also reorganised
dispatch_function_versions and aarch64_mangle_decl_assembler_name, along with
several other minor fixes.
The updated series passes regression testing on both aarch64 for C and C++.
The previous version passed testing on x86; I haven't retested it since.
Ok for master?
Thanks,
Andrew
next reply other threads:[~2023-12-06 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 12:43 Andrew Carlotti [this message]
2023-12-06 12:44 ` [1/5] aarch64: Add cpu feature detection to libgcc Andrew Carlotti
2023-12-06 12:45 ` [PATCH v3 2/5] c-family: Simplify attribute exclusion handling Andrew Carlotti
2023-12-06 12:45 ` [PATCH v3 3/5] ada: Improve " Andrew Carlotti
2023-12-06 12:46 ` [PATCH v3 4/5] Add support for target_version attribute Andrew Carlotti
2023-12-14 14:58 ` Richard Sandiford
2023-12-16 0:45 ` [committed v4 " Andrew Carlotti
2023-12-06 12:47 ` [PATCH v3 5/5] aarch64: Add function multiversioning support Andrew Carlotti
2023-12-14 14:02 ` Richard Sandiford
2023-12-16 0:47 ` [committed v4 " Andrew Carlotti
2023-12-16 4:03 ` Ramana Radhakrishnan
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=4cdd7089-edd4-96b9-5c0e-120d5357f01b@e124511.cambridge.arm.com \
--to=andrew.carlotti@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).