public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Haochen Jiang <haochen.jiang@intel.com>, binutils@sourceware.org
Subject: Re: [PATCH 3/6] Support Intel CMPccXADD
Date: Wed, 2 Nov 2022 09:25:30 -0700	[thread overview]
Message-ID: <CAMe9rOq-+rLCWPGo4d3HgxbujC9XMFX_pBsgEHA1yuDpjJh4zA@mail.gmail.com> (raw)
In-Reply-To: <3666195d-32ac-62b8-a03d-41a3bb0bc32b@suse.com>

On Wed, Nov 2, 2022 at 3:52 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 31.10.2022 04:05, Haochen Jiang wrote:
> > --- a/gas/config/tc-i386.c
> > +++ b/gas/config/tc-i386.c
> > @@ -1098,6 +1098,7 @@ static const arch_entry cpu_arch[] =
> >    SUBARCH (prefetchi, PREFETCHI, ANY_PREFETCHI, false),
> >    SUBARCH (avx_ifma, AVX_IFMA, ANY_AVX_IFMA, false),
> >    SUBARCH (avx_vnni_int8, AVX_VNNI_INT8, ANY_AVX_VNNI_INT8, false),
> > +  SUBARCH (cmpccxadd, CMPCCXADD, ANY_CMPCCXADD, false),
>
> ANY_CMPCCXADD shouldn't have been re-introduced here. It now being
> there only means more code churn in my patch to sanitize all of this
> dependencies handling. (Unless, as I'll mention there as an option,
> we want to uniformly use ANY_... in [almost] all table entries).

We discussed it.  ANY_ doesn't hurt and it can be useful when there is
a dependency in the future.

> > --- a/opcodes/i386-opc.h
> > +++ b/opcodes/i386-opc.h
> > @@ -215,6 +215,8 @@ enum
> >    CpuAVX_IFMA,
> >    /* Intel AVX VNNI-INT8 Instructions support required.  */
> >    CpuAVX_VNNI_INT8,
> > +  /* Intel CMPccXADD instructions support required.  */
> > +  CpuCMPCCXADD,
>
> Just as a remark: Personally I would have considered it more readable
> overall if this had the "CC" infix in lower case (like in the comment).
>
> Jan



-- 
H.J.

  reply	other threads:[~2022-11-02 16:26 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
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 [this message]
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=CAMe9rOq-+rLCWPGo4d3HgxbujC9XMFX_pBsgEHA1yuDpjJh4zA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=haochen.jiang@intel.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).