From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>, Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, "Mo, Zewei" <zewei.mo@intel.com>
Subject: RE: [PATCH] x86: drop redundant EVex128 from PUSH2/POP2
Date: Thu, 18 Jan 2024 01:35:52 +0000 [thread overview]
Message-ID: <SJ0PR11MB5600A6FF8812D09F72131E509E712@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c39fa6ba-927c-4828-bb65-69bc8a774535@suse.com>
> EVexMap4 already covers that.
>
> --- a/opcodes/i386-opc.tbl
> +++ b/opcodes/i386-opc.tbl
> @@ -3494,9 +3494,9 @@ uwrmsr, 0xf3f8/0, APX_F(USER_MSR), Modrm
>
> // APX Push2/Pop2 instructions.
>
> -push2, 0xff/6, APX_F,
> Modrm|VexW0|EVex128|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf
> |No_sSuf, { Reg64, Reg64 } -push2p, 0xff/6, APX_F,
> Modrm|VexW1|EVex128|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf
> |No_sSuf, { Reg64, Reg64 } -pop2, 0x8f/0, APX_F,
> Modrm|VexW0|EVex128|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf
> |No_sSuf, { Reg64, Reg64 } -pop2p, 0x8f/0, APX_F,
> Modrm|VexW1|EVex128|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf
> |No_sSuf, { Reg64, Reg64 }
> +push2, 0xff/6, APX_F,
> +Modrm|VexW0|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf|No_sSu
> f, { Reg64,
> +Reg64 } push2p, 0xff/6, APX_F,
> +Modrm|VexW1|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf|No_sSu
> f, { Reg64,
> +Reg64 } pop2, 0x8f/0, APX_F,
> +Modrm|VexW0|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf|No_sSu
> f, { Reg64,
> +Reg64 } pop2p, 0x8f/0, APX_F,
> +Modrm|VexW1|EVexMap4|VexVVVV|No_bSuf|No_wSuf|No_lSuf|No_sSu
> f, { Reg64,
> +Reg64 }
>
> // APX Push2/Pop2 instructions end.
It's OK and thanks.
Lili.
prev parent reply other threads:[~2024-01-18 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:58 Jan Beulich
2024-01-18 1:35 ` Cui, Lili [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=SJ0PR11MB5600A6FF8812D09F72131E509E712@SJ0PR11MB5600.namprd11.prod.outlook.com \
--to=lili.cui@intel.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=zewei.mo@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).