From: Tamar Christina <Tamar.Christina@arm.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Cc: nd <nd@arm.com>, Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
"nickc@redhat.com" <nickc@redhat.com>
Subject: RE: [PATCH][Binutils]AArch64 Enable FP16 by default for Armv9-A.
Date: Tue, 17 May 2022 10:09:39 +0000 [thread overview]
Message-ID: <VI1PR08MB53255E8D86E13EF5C5D5007DFFCE9@VI1PR08MB5325.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <d3da7d0a-5310-197c-6a46-5106565ac9b4@foss.arm.com>
>
> On 16/05/2022 17:10, Tamar Christina via Binutils wrote:
> > Hi All,
> >
> > In Armv9-A SVE is mandatory, and for SVE FP16 is mandatory. This
> > fixes a disconnect between GCC and binutils where GCC has FP16 on by
> default and gas doesn't.
> >
> > build on native hardware and regtested on aarch64-none-linux-gnu and no
> issues.
> >
> > Ok for master? and for backport to binutils-2.38?
> >
>
> OK for master. I think you'll need Nick to approve a backport, though.
> I would recommend that.
>
Ah ok, Nick, permission to backport to 2.38?
Cheers,
Tamar
> R.
>
> > Thanks,
> > Tamar
> >
> > include/ChangeLog:
> >
> > 2022-05-16 Tamar Christina <tamar.christina@arm.com>
> >
> > * opcode/aarch64.h (AARCH64_ARCH_V9_FEATURES): Add
> AARCH64_FEATURE_F16.
> >
> > --- inline copy of patch --
> > diff --git a/include/opcode/aarch64.h b/include/opcode/aarch64.h index
> >
> a4912930c8f1e564bec6ec46a649ac1205093bd1..8fe27900cba3e897880a3966cc
> 2a
> > 17e89dbdf018 100644
> > --- a/include/opcode/aarch64.h
> > +++ b/include/opcode/aarch64.h
> > @@ -140,6 +140,7 @@ typedef uint32_t aarch64_insn;
> > | AARCH64_FEATURE_HBC)
> >
> > #define AARCH64_ARCH_V9_FEATURES (AARCH64_FEATURE_V9
> \
> > + | AARCH64_FEATURE_F16 \
> > | AARCH64_FEATURE_SVE
> \
> > | AARCH64_FEATURE_SVE2)
> > #define AARCH64_ARCH_V9_1_FEATURES
> (AARCH64_ARCH_V8_6_FEATURES)
> >
> >
> >
> >
next prev parent reply other threads:[~2022-05-17 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 16:10 Tamar Christina
2022-05-17 9:56 ` Richard Earnshaw
2022-05-17 10:09 ` Tamar Christina [this message]
2022-05-18 16:29 ` Nick Clifton
2022-06-16 13:19 ` Nick Clifton
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=VI1PR08MB53255E8D86E13EF5C5D5007DFFCE9@VI1PR08MB5325.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=nd@arm.com \
--cc=nickc@redhat.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).