From: Jan Beulich <jbeulich@suse.com>
To: Haochen Jiang <haochen.jiang@intel.com>
Cc: hjl.tools@gmail.com, "Cui,Lili" <lili.cui@intel.com>,
binutils@sourceware.org
Subject: Re: [PATCH 2/6] Support Intel AVX-VNNI-INT8
Date: Wed, 2 Nov 2022 11:45:53 +0100 [thread overview]
Message-ID: <eb54610c-4252-65a6-b9d7-68e9d222f675@suse.com> (raw)
In-Reply-To: <20221031030507.35588-3-haochen.jiang@intel.com>
On 31.10.2022 04:05, Haochen Jiang wrote:
> @@ -7575,11 +7592,11 @@ static const struct dis386 vex_w_table[][2] = {
> },
> {
> /* VEX_W_0F3850 */
> - { "%XVvpdpbusd", { XM, Vex, EXx }, PREFIX_DATA },
> + { PREFIX_TABLE (PREFIX_VEX_0F3850_W_0) },
> },
> {
> - /* VEX_W_0F3851 */
> - { "%XVvpdpbusds", { XM, Vex, EXx }, PREFIX_DATA },
> + /* VEX_W_0F3851_P_0 */
> + { PREFIX_TABLE (PREFIX_VEX_0F3851_W_0) },
Note that the comment is now wrong - it shouldn't have been changed (just
like the earlier one was left untouched).
Jan
next prev parent reply other threads:[~2022-11-02 10:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 3:05 [PATCH v4 0/6] Support Intel Sierra Forest Instructions Haochen Jiang
2022-10-31 3:05 ` [PATCH 1/6] Support Intel AVX-IFMA Haochen Jiang
2022-10-31 16:52 ` H.J. Lu
2022-10-31 3:05 ` [PATCH 2/6] Support Intel AVX-VNNI-INT8 Haochen Jiang
2022-10-31 16:53 ` H.J. Lu
2022-11-02 10:45 ` Jan Beulich [this message]
2022-10-31 3:05 ` [PATCH 3/6] Support Intel CMPccXADD Haochen Jiang
2022-10-31 16:54 ` H.J. Lu
2022-11-02 10:52 ` Jan Beulich
2022-11-02 16:25 ` H.J. Lu
2022-10-31 3:05 ` [PATCH 4/6] Add handler for more i386_cpu_flags Haochen Jiang
2022-10-31 16:54 ` H.J. Lu
2022-10-31 3:05 ` [PATCH 5/6] Support Intel WRMSRNS Haochen Jiang
2022-10-31 16:56 ` H.J. Lu
2022-11-02 10:56 ` Jan Beulich
2022-11-02 14:35 ` Jan Beulich
2022-10-31 3:05 ` [PATCH 6/6] Support Intel MSRLIST Haochen Jiang
2022-10-31 16:55 ` 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=eb54610c-4252-65a6-b9d7-68e9d222f675@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=haochen.jiang@intel.com \
--cc=hjl.tools@gmail.com \
--cc=lili.cui@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).