From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: x86 ISA v3 / v4 coverage
Date: Thu, 2 Jun 2022 16:31:39 +0200 [thread overview]
Message-ID: <c0960d4f-868c-fc5b-8ed4-eca0e990d822@suse.com> (raw)
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?
Shouldn't AVX512_4FMAPS be excluded from v4, just like AVX512_4VNNIW is?
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
excluded from v3 when it was added to the code base. And e.g. GFNI is not
part of v2 because there no "umbrella property" (VEX for v3, EVEX for v4)
is checked, but it's strictly a white-listing of Cpu* flags.
I'm afraid all of this once again is unobvious because the specification
is not clear enough.
Jan
next reply other threads:[~2022-06-02 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 14:31 Jan Beulich [this message]
2022-06-02 15:29 ` H.J. Lu
2022-06-07 13:13 ` Michael Matz
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=c0960d4f-868c-fc5b-8ed4-eca0e990d822@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).