From: Kyrylo Tkachov <ktkachov@nvidia.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] aarch64: Add support for -mcpu=grace
Date: Thu, 27 Jun 2024 06:52:30 +0000 [thread overview]
Message-ID: <CFD1DE11-AA21-4893-A068-7FA33F870F89@nvidia.com> (raw)
In-Reply-To: <CA+=Sn1n4HkWfnAvfJ4jbLa+puZPq8b_43pxYJxQBLLLsN38oVw@mail.gmail.com>
Hi Andrew,
> On 26 Jun 2024, at 23:02, Andrew Pinski <pinskia@gmail.com> wrote:
>
> External email: Use caution opening links or attachments
>
>
> On Wed, Jun 26, 2024 at 12:40 AM Kyrylo Tkachov <ktkachov@nvidia.com> wrote:
>>
>> Hi all,
>>
>> This adds support for the NVIDIA Grace CPU to aarch64.
>> We reuse the tuning decisions for the Neoverse V2 core, but include a
>> number of architecture features that are not enabled by default in
>> -mcpu=neoverse-v2.
>>
>> This allows Grace users to more simply target the CPU with -mcpu=grace
>> rather than remembering what extensions to tag on top of
>> -mcpu=neoverse-v2.
>>
>> Bootstrapped and tested on aarch64-none-linux-gnu.
>> I’m pushing this to trunk.
>
>> RNG
>
> I noticed this is missing from grace but is included in neoverse-v2.
> Is that expected?
Yes, RNG is an optional configuration feature of Neoverse V2 (according to the TRM) and Grace doesn’t implement it. In fact, I don’t think the base -mcpu=neoverse-v2 should include it either (I’m testing a patch to remove it)
Thanks,
Kyrill
>
> Thanks,
> Andrew Pinski
>
>
>> I have patches tested for the 14, 13, 12, 11 branches as well that I’d like to push there to make it simpler for our users to target Grace.
>> They are the same as this one logically, but they just account for slight syntactic differences and flag definitions that have happened since those branches.
>> Thanks,
>> Kyrill
>>
>> * config/aarch64/aarch64-cores.def (grace): New entry.
>> * config/aarch64/aarch64-tune.md: Regenerate
>> * doc/invoke.texi (AArch64 Options): Document the above.
>>
>> Signed-off-by: Kyrylo Tkachov <ktkachov@nvidia.com>
prev parent reply other threads:[~2024-06-27 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 7:39 Kyrylo Tkachov
2024-06-26 21:02 ` Andrew Pinski
2024-06-27 6:52 ` Kyrylo Tkachov [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=CFD1DE11-AA21-4893-A068-7FA33F870F89@nvidia.com \
--to=ktkachov@nvidia.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.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).