gcc-patches@gcc.gnu.org<mailto:gcc-patches@gcc.gnu.org>; Richard Earnshaw
mailto:richard.earns...@arm.com>>;
Richard Sandiford mailto:richard.sandif...@arm.com>>
Subject: Re: [PATCH] aarch64: Remove RNG and MTE from -mcpu=neoverse-v2
Hi Tamar,
Thanks for going through the docs h
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Thursday, June 27, 2024 3:49 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; Richard Earnshaw ;
> Richard Sandiford
> Subject: Re: [PATCH] aarch64: Remove RNG and MTE from -mcpu=neoverse-v2
>
> H
rsday, June 27, 2024 9:58 AM
>> To: gcc-patches@gcc.gnu.org
>> Cc: Richard Earnshaw ; Richard Sandiford
>>
>> Subject: [PATCH] aarch64: Remove RNG and MTE from -mcpu=neoverse-v2
>>
>> Hi all,
>>
>> According to the TRM for Neoverse V2 the Memory Ta
Hi Kyrill,
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Thursday, June 27, 2024 9:58 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Richard Earnshaw ; Richard Sandiford
>
> Subject: [PATCH] aarch64: Remove RNG and MTE from -mcpu=neoverse-v2
>
> Hi all,
&g
Hi all,
According to the TRM for Neoverse V2 the Memory Tagging and RNG features
are optional configurations of the core and may not always be present.
Therefore -mcpu=neoverse-v2 shouldn't enable them, similar to how the crypto
extensions aren’t enabled by default.
Bootstrapped and tested on aa
