public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Beulich <jbeulich@suse.com>, Binutils <binutils@sourceware.org>
Subject: Re: x86 ISA v3 / v4 coverage
Date: Tue, 7 Jun 2022 13:13:20 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LSU.2.20.2206071310070.12633@wotan.suse.de> (raw)
In-Reply-To: <CAMe9rOrZSRGO3zQXGAK_rEwHkRFtJSAGEZe1WC1TDwZLjg-W7A@mail.gmail.com>

Hello,

On Thu, 2 Jun 2022, H.J. Lu via Binutils wrote:

> On Thu, Jun 2, 2022 at 7:31 AM Jan Beulich <jbeulich@suse.com> wrote:
> >
> > H.J.,
> >
> > the other day I came to notice two apparent anomalies:
> >
> > Shouldn't XOP and FMA4 be excluded from v3, just like LWP and TBM are?
> 
> Yes, they should be excluded since they don't require v3.
> 
> > Shouldn't AVX512_4FMAPS be excluded from v4, just like AVX512_4VNNIW is?
> 
> Yes, it should be since it doesn't require v4.
> 
> > And is it correct for new ISA additions (like not so long ago AVX512-FP16)
> > to become part of what is covered by v3 or v4? AMX, for example, was
> 
> AVX512_FP16 requires v4.

But it can't be part of v3 or v4.  New ISA additions never can become 
part of an existing ISA level, once it's released it's fixated.  I just 
wanted to state this explicitely because it seems Jan used "part of vX" 
to mean "binaries stating to require vX can use ISA feature so-and-so", 
whereas you seem to mean "ISA feature so-and-so requires at least vX".


Ciao,
Michael.

  reply	other threads:[~2022-06-07 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 14:31 Jan Beulich
2022-06-02 15:29 ` H.J. Lu
2022-06-07 13:13   ` Michael Matz [this message]
2022-06-07 21:39     ` H.J. Lu
2022-06-08 11:09       ` Michael Matz

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=alpine.LSU.2.20.2206071310070.12633@wotan.suse.de \
    --to=matz@suse.de \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=jbeulich@suse.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).