public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Haochen Jiang <haochen.jiang@intel.com>
To: binutils@sourceware.org
Cc: jbeulich@suse.com, hjl.tools@gmail.com
Subject: [PATCH v4 0/6] Support Intel Sierra Forest Instructions
Date: Mon, 31 Oct 2022 11:05:01 +0800	[thread overview]
Message-ID: <20221031030507.35588-1-haochen.jiang@intel.com> (raw)

Hi all,

These six patches are our v4 patch for new ISAs.

For these six patches, only minor fixes are done comparing to v3.
All the comments mentioned in previous thread are fixed, including:

1. Add _ANY_ back to all ISAs.

2. Share the test dump file between 32/64 bits for WRMSRNS/MSRLIST.

3. Adjust the insertion in opcodes/i386-opc.tbl for AVX-IFMA and
AVX-VNNI-INT8.

4. Remove SwapSource usage in CMPccXADD and use cpuarch to handle
the special encoding in CMPccXADD.

Thanks for all the discussion and reviews. Ok for trunk?

BTW, there are still two patches pending for revise so they are
not included in this series. AVX-NE-CONVERT will be sent out soon
and RAO-INT still pending for the discussion on suffixes usage.

BRs,
Haochen



             reply	other threads:[~2022-10-31  3:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  3:05 Haochen Jiang [this message]
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
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=20221031030507.35588-1-haochen.jiang@intel.com \
    --to=haochen.jiang@intel.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --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).