public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Srinath Parvathaneni <srinath.parvathaneni@arm.com>,
	Nick Clifton <nickc@redhat.com>
Cc: 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: Tue, 13 Feb 2024 08:24:14 +0100	[thread overview]
Message-ID: <996e95da-10dd-44ba-8e00-26a76fd8a61c@suse.com> (raw)
In-Reply-To: <e312301e-9cca-4a54-9263-07a15936aa71@arm.com>

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? 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

  reply	other threads:[~2024-02-13  7:24 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 [this message]
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

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=996e95da-10dd-44ba-8e00-26a76fd8a61c@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --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).