From: Andrew Carlotti <andrew.carlotti@arm.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Srinath Parvathaneni <srinath.parvathaneni@arm.com>,
Nick Clifton <nickc@redhat.com>,
Binutils <binutils@sourceware.org>,
Richard Earnshaw <rearnsha@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>
Subject: Re: your patches enabling Arm64's SVE 2.1 extension
Date: Thu, 15 Feb 2024 11:21:40 +0000 [thread overview]
Message-ID: <a3c8d302-c18d-c6ba-9152-2a926e37829b@e124511.cambridge.arm.com> (raw)
In-Reply-To: <996e95da-10dd-44ba-8e00-26a76fd8a61c@suse.com>
On Tue, Feb 13, 2024 at 08:24:14AM +0100, Jan Beulich wrote:
> On 13.02.2024 00:16, Srinath Parvathaneni wrote:
> > On 2/12/2024 8:00 AM, Jan Beulich wrote:
> >> 7) orqv, pmov, tblq, tbxq, uzpq{1,2}, and zipq{1,2} are entirely missing.
> >
> > I'm aware the above mentioned instructions are missing in binutils and
> > I'm currently
> >
> > working on adding support for these instructions. I will update you once
> > the patches
> >
> > are committed.
>
> In which case - what is the gas/NEWS entry about?
I added the gas/NEWS entry because my expectation was that we wouldn't have
added only partial support for the extension (at least not without clearly
marking it as such). I wasn't aware of any issues with our SVE 2.1 support
until after the 2.42 release; otherwise I would have modified gas/NEWS and
suggested disabling the flag until the next release.
> Just in case there would
> be a 2.42.1, may I ask that it be purged at least there, and perhaps also
> from the main branch, until support is actually complete? Alternatively,
> Nick, once support is complete maybe that's then really a(nother) reason
> to cut a 2.42.1?
>
> Jan
prev parent reply other threads:[~2024-02-15 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 8:00 Jan Beulich
2024-02-12 23:16 ` Srinath Parvathaneni
2024-02-13 7:24 ` Jan Beulich
2024-02-13 9:55 ` Nick Clifton
2024-02-13 10:48 ` Jan Beulich
2024-02-13 11:11 ` Nick Clifton
2024-02-13 11:39 ` Jan Beulich
2024-03-11 7:14 ` Jan Beulich
2024-02-15 11:21 ` Andrew Carlotti [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=a3c8d302-c18d-c6ba-9152-2a926e37829b@e124511.cambridge.arm.com \
--to=andrew.carlotti@arm.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=marcus.shawcroft@arm.com \
--cc=nickc@redhat.com \
--cc=rearnsha@arm.com \
--cc=srinath.parvathaneni@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).