public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Cui, Lili" <lili.cui@intel.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: add missing APX logic to cpu_flags_match()
Date: Mon, 8 Jan 2024 09:58:49 +0100	[thread overview]
Message-ID: <11d23d18-142c-4c32-bab2-6ddfd9257051@suse.com> (raw)
In-Reply-To: <SJ0PR11MB56001261D206BD473685168B9E6B2@SJ0PR11MB5600.namprd11.prod.outlook.com>

On 08.01.2024 09:30, Cui, Lili wrote:
>>>> --- a/gas/config/tc-i386.c
>>>> +++ b/gas/config/tc-i386.c
>>>> @@ -1940,6 +1940,30 @@ cpu_flags_match (const insn_template *t)
>>>>  	      any.bitfield.cpuavx512vl = 0;
>>>>  	    }
>>>>  	}
>>>> +
>>>> +      /* Dual non-APX/APX templates need massaging from what APX_F() in
>> the
>>>> +         opcode table has produced.  While the direct transformation of the
>>>> +         incoming cpuid&(cpuid|APX_F) would be to cpuid&(cpuid) /
>>>> cpuid&(APX_F)
>>>> +         respectively, it's cheaper to move to just cpuid / cpuid&APX_F
>>>> +         instead.  */
>>>> +      if (any.bitfield.cpuapx_f
>>>> +	  && (any.bitfield.cpubmi || any.bitfield.cpubmi2
>>>> +	      || any.bitfield.cpuavx512f || any.bitfield.cpuavx512bw
>>>> +	      || any.bitfield.cpuavx512dq || any.bitfield.cpuamx_tile
>>>> +	      || any.bitfield.cpucmpccxadd))
>>>> +	{
>>>> +	  /* These checks (verifying that APX_F() was properly used in the
>>>> +	     opcode table entry) make sure there's no need for an "else" to
>>>> +	     the "if()" below.  */
>>>> +	  gas_assert (!cpu_flags_all_zero (&all));
>>>> +	  cpu = cpu_flags_and (all, any);
>>>> +	  gas_assert (cpu_flags_equal (&cpu, &all));
>>>> +
>>>> +	  if (need_evex_encoding (t))
>>>> +	    all = any;
>>>> +
>>>
>>>> +	  memset (&any, 0, sizeof (any));
>>>
>>> Wouldn't it make sense to put it in the else branch and clean out APX-F
>> specifically? Just like you did before.
>>>
>>>   if (need_evex_encoding (t))
>>>     all = any;
>>> else
>>>    any.bitfield.cpuapx_f = 0;
>>
>> That was an alternative I did consider, yes, but the way I've done it is overall
>> more self-consistent imo, at the expense of being less consistent with the
>> AVX/AVX512 logic (the moving of "any" to "all" isn't consistent with that
>> anyway).
>>
> 
>   memset (&any, 0, sizeof (any)); 
> 
> I'd say this would make "any" not match the actual value, which might be used later, but it's been cleared here.

I'm afraid I don't get what you're trying to tell me.

Jan

  reply	other threads:[~2024-01-08  8:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 12:15 Jan Beulich
2024-01-08  3:17 ` Cui, Lili
2024-01-08  7:56   ` Jan Beulich
2024-01-08  8:30     ` Cui, Lili
2024-01-08  8:58       ` Jan Beulich [this message]
2024-01-08 10:28         ` Cui, Lili
2024-01-08 10:38           ` Jan Beulich
2024-01-09  5:36             ` Cui, Lili
2024-01-09  8:30               ` Jan Beulich
2024-01-09 11:00                 ` Cui, Lili
2024-01-09 11:07                   ` Jan Beulich
2024-01-10  1:44                     ` Cui, Lili

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=11d23d18-142c-4c32-bab2-6ddfd9257051@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --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).