From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Srinath Parvathaneni <Srinath.Parvathaneni@arm.com>,
gcc Patches <gcc-patches@gcc.gnu.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Subject: Re: [GCC][PATCH v4] arm: Add pacbti related multilib support for armv8.1-m.main.
Date: Fri, 20 Jan 2023 17:06:08 +0000 [thread overview]
Message-ID: <914e3eb3-a77d-98b9-1fcd-7169fe79f517@foss.arm.com> (raw)
In-Reply-To: <VE1PR08MB48932F30DEA3BD35AD63F40B9BC29@VE1PR08MB4893.eurprd08.prod.outlook.com>
On 13/01/2023 17:46, Srinath Parvathaneni via Gcc-patches wrote:
> Hi,
>
> This patch adds the support for pacbti multlilib linking by making
> "-mbranch-protection=none" as default multilib option for arm-none-eabi
> target.
>
> Eg 1.
>
> If the passed command line flags are (without mbranch-protection):
> a) -march=armv8.1-m.main+mve -mfloat-abi=hard -mfpu=auto
>
> "-mbranch-protection=none" will be used in the multilib matching.
>
> Eg 2.
>
> If the passed command line flags are (with mbranch-protection):
> a) -march=armv8.1-m.main+mve+pacbti -mfloat-abi=hard -mfpu=auto -mbranch-protection=pac-ret
>
> "-mbranch-protection=standard" will be used in the multilib matching.
>
> Regression tested on arm-none-eabi and bootstrapped on arm-none-linux-gnueabihf.
>
> Ok for master?
>
> Regards,
> Srinath.
>
> gcc/ChangeLog:
>
> 2023-01-11 Srinath Parvathaneni <srinath.parvathaneni@arm.com>
>
> * config.gcc ($tm_file): Update variable.
> * config/arm/arm-mlib.h: Create new header file.
> * config/arm/t-rmprofile (MULTI_ARCH_DIRS_RM): Rename mbranch-protection
> multilib arch directory.
> (MULTILIB_REUSE): Add multilib reuse rules.
> (MULTILIB_MATCHES): Add multilib match rules.
>
> gcc/testsuite/ChangeLog:
>
> 2023-01-11 Srinath Parvathaneni <srinath.parvathaneni@arm.com>
>
> * gcc.target/arm/multilib.exp (multilib_config "rmprofile"): Update
> tests.
> * gcc.target/arm/pac-12.c: New test.
> * gcc.target/arm/pac-13.c: Likewise.
> * gcc.target/arm/pac-14.c: Likewise.
OK.
R.
prev parent reply other threads:[~2023-01-20 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 17:46 Srinath Parvathaneni
2023-01-20 17:06 ` Richard Earnshaw [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=914e3eb3-a77d-98b9-1fcd-7169fe79f517@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Srinath.Parvathaneni@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).