From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: properly decode EVEX.W for AVX512_4{FMAPS,VNNIW} insns
Date: Fri, 14 Oct 2022 10:29:50 -0700 [thread overview]
Message-ID: <CAMe9rOr=WXUQko9K6Kn6OJHZ=jgkPRxUh91t3LYwJgK2m+NcCA@mail.gmail.com> (raw)
In-Reply-To: <9fd2c88d-98b2-99a4-419f-c7235b2cf960@suse.com>
On Fri, Oct 14, 2022 at 7:11 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> These require EVEX.W=0. Use %XS to facilitate the checking, even if for
> the AVX512_4VNNIW ones this is kind of an abuse (as 's' there stands for
> "signed", not "single").
>
> While there also correct the 3rd operand for the AVX512_4VNNIW entries:
> Only the memory form is allowed (just like for AVX512_4FMAPS, where the
> correct type is already in use).
> ---
> This goes on top of "x86: fold AVX512-VNNI disassembler entries with
> AVX-VNNI ones", submitted earlier today.
>
> --- a/opcodes/i386-dis-evex-prefix.h
> +++ b/opcodes/i386-dis-evex-prefix.h
> @@ -234,14 +234,14 @@
> { Bad_Opcode },
> { "vdpbf16p%XS", { XM, Vex, EXx }, 0 },
> { VEX_W_TABLE (VEX_W_0F3852) },
> - { "vp4dpwssd", { XM, Vex, EXxmm }, 0 },
> + { "vp4dpws%XSd", { XM, Vex, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F3853 */
> {
> { Bad_Opcode },
> { Bad_Opcode },
> { VEX_W_TABLE (VEX_W_0F3853) },
> - { "vp4dpwssds", { XM, Vex, EXxmm }, 0 },
> + { "vp4dpws%XSds", { XM, Vex, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F3868 */
> {
> @@ -262,28 +262,28 @@
> { Bad_Opcode },
> { Bad_Opcode },
> { "vfmsub132p%XW", { XM, Vex, EXx, EXxEVexR }, 0 },
> - { "v4fmaddps", { XM, Vex, Mxmm }, 0 },
> + { "v4fmaddp%XS", { XM, Vex, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F389B */
> {
> { Bad_Opcode },
> { Bad_Opcode },
> { "vfmsub132s%XW", { XMScalar, VexScalar, EXdq, EXxEVexR }, 0 },
> - { "v4fmaddss", { XMScalar, VexScalar, Mxmm }, 0 },
> + { "v4fmadds%XS", { XMScalar, VexScalar, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F38AA */
> {
> { Bad_Opcode },
> { Bad_Opcode },
> { "vfmsub213p%XW", { XM, Vex, EXx, EXxEVexR }, 0 },
> - { "v4fnmaddps", { XM, Vex, Mxmm }, 0 },
> + { "v4fnmaddp%XS", { XM, Vex, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F38AB */
> {
> { Bad_Opcode },
> { Bad_Opcode },
> { "vfmsub213s%XW", { XMScalar, VexScalar, EXdq, EXxEVexR }, 0 },
> - { "v4fnmaddss", { XMScalar, VexScalar, Mxmm }, 0 },
> + { "v4fnmadds%XS", { XMScalar, VexScalar, Mxmm }, 0 },
> },
> /* PREFIX_EVEX_0F3A08 */
> {
OK.
Thanks.
--
H.J.
prev parent reply other threads:[~2022-10-14 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 14:11 Jan Beulich
2022-10-14 17:29 ` H.J. Lu [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='CAMe9rOr=WXUQko9K6Kn6OJHZ=jgkPRxUh91t3LYwJgK2m+NcCA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--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).