public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>,
	Srinath Parvathaneni <srinath.parvathaneni@arm.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 09:55:38 +0000	[thread overview]
Message-ID: <f9d06c98-21fe-42c3-ae06-38691acd8f2c@redhat.com> (raw)
In-Reply-To: <996e95da-10dd-44ba-8e00-26a76fd8a61c@suse.com>

Hi Jan, Hi Srinath,
> 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?

I would agree with this.

> Alternatively,
> Nick, once support is complete maybe that's then really a(nother) reason
> to cut a 2.42.1?

Hmmm... this is a hard decision.  Normally I would only consider a point release
if we needed to fix an important bug - one which could result in incorrect code
generation or total failure of a tool like the linker or assembler.  But a release
just to add some missing instructions which were supposed to be supported but were
actually not ... well that does not seem to me to be a good enough reason.

Unless - how significant are these instructions ?  I have not actually looked
into their semantics.  Are there needed in order for a kernel to be able to
access specific features of the AArch64 architecture ?  Are they essential for
atomic operations ?  Are they even likely to be produced by a compiler ?

Basically if they are not critical to the infrastructure of an operating system,
then I do not think that they justify a point release.

Cheers
   Nick



  reply	other threads:[~2024-02-13  9:55 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 [this message]
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=f9d06c98-21fe-42c3-ae06-38691acd8f2c@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=marcus.shawcroft@arm.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).