From: Jan Beulich <jbeulich@suse.com>
To: "Kong, Lingling" <lingling.kong@intel.com>,
"Jiang, Haochen" <haochen.jiang@intel.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH 2/2] Support Intel AVX-NE-CONVERT
Date: Wed, 2 Nov 2022 08:47:21 +0100 [thread overview]
Message-ID: <d1ea9b1f-9c81-631c-446f-c2aacf63e637@suse.com> (raw)
In-Reply-To: <DM4PR11MB54878120BDB7EF2CC932EFD6EC369@DM4PR11MB5487.namprd11.prod.outlook.com>
On 01.11.2022 10:04, Kong, Lingling wrote:
> --- a/opcodes/i386-dis.c
> +++ b/opcodes/i386-dis.c
> @@ -942,6 +942,8 @@ enum
> MOD_VEX_0F385E_X86_64_P_3_W_0,
> MOD_VEX_0F388C,
> MOD_VEX_0F388E,
> + MOD_VEX_0F38B0,
> + MOD_VEX_0F38B1,
> MOD_VEX_0F3A30_L_0,
> MOD_VEX_0F3A31_L_0,
> MOD_VEX_0F3A32_L_0,
> @@ -1140,6 +1142,9 @@ enum
> PREFIX_VEX_0F3851_W_0,
> PREFIX_VEX_0F385C_X86_64,
> PREFIX_VEX_0F385E_X86_64,
> + PREFIX_VEX_0F3872,
> + PREFIX_VEX_0F38B0_M_0_W_0,
> + PREFIX_VEX_0F38B1_M_0_W_0,
> PREFIX_VEX_0F38F5_L_0,
> PREFIX_VEX_0F38F6_L_0,
> PREFIX_VEX_0F38F7_L_0,
> @@ -1556,8 +1561,11 @@ enum
> VEX_W_0F385E_X86_64_P_1,
> VEX_W_0F385E_X86_64_P_2,
> VEX_W_0F385E_X86_64_P_3,
> + VEX_W_0F3872_P_1,
> VEX_W_0F3878,
> VEX_W_0F3879,
> + VEX_W_0F38B0_M_0,
> + VEX_W_0F38B1_M_0,
> VEX_W_0F38B4,
> VEX_W_0F38B5,
> VEX_W_0F38CF,
> @@ -4093,6 +4101,27 @@ static const struct dis386 prefix_table[][4] = {
> { VEX_W_TABLE (VEX_W_0F385E_X86_64_P_3) },
> },
>
> + /* PREFIX_VEX_0F3872 */
> + {
> + { Bad_Opcode },
> + { VEX_W_TABLE (VEX_W_0F3872_P_1) },
> + },
> +
> + /* PREFIX_VEX_0F38B0_M_0_W_0 */
> + {
> + { "vcvtneoph2ps", { XM, Mx }, 0 },
> + { "vcvtneebf162ps", { XM, Mx }, 0 },
> + { "vcvtneeph2ps", { XM, Mx }, 0 },
> + { "vcvtneobf162ps", { XM, Mx }, 0 },
> + },
With the use of Mx here I see no reason to have decode go through
mod_table[]. And then ...
> + /* PREFIX_VEX_0F38B1_M_0_W_0 */
> + {
> + { Bad_Opcode },
> + { "vbcstnebf162ps", { XM, Ew }, 0 },
> + { "vbcstnesh2ps", { XM, Ew }, 0 },
> + },
... this should also engage OP_M() rather than OP_E(), removing the
mod_table[] decode step here as well. Obviously you'll need to add
Mw for that to work.
Jan
next prev parent reply other threads:[~2022-11-02 7:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 6:05 [PATCH v4 0/2] " Haochen Jiang
2022-10-31 6:06 ` [PATCH 1/2] i386: Add <Vxy> and <Exy> Haochen Jiang
2022-10-31 9:04 ` Jan Beulich
2022-10-31 16:30 ` H.J. Lu
2022-11-01 8:50 ` Kong, Lingling
2022-11-01 14:42 ` H.J. Lu
2022-10-31 6:06 ` [PATCH 2/2] Support Intel AVX-NE-CONVERT Haochen Jiang
2022-10-31 9:14 ` Jan Beulich
2022-11-01 1:24 ` Jiang, Haochen
2022-11-01 6:50 ` Jan Beulich
2022-11-01 8:08 ` Kong, Lingling
2022-11-01 9:04 ` Kong, Lingling
2022-11-02 7:47 ` Jan Beulich [this message]
2022-11-02 8:50 ` Kong, Lingling
2022-11-02 9:53 ` Jan Beulich
2022-11-03 2:44 ` H.J. Lu
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=d1ea9b1f-9c81-631c-446f-c2aacf63e637@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=haochen.jiang@intel.com \
--cc=hjl.tools@gmail.com \
--cc=lingling.kong@intel.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).