public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Cui, Lili" <lili.cui@intel.com>
To: "Beulich, Jan" <JBeulich@suse.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH 1/3] x86: Split REX/REX2 old registers judgment.
Date: Wed, 22 May 2024 01:33:53 +0000	[thread overview]
Message-ID: <SJ0PR11MB560068F18F93981C894C0E829EEB2@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <241011a5-1240-4a56-8749-ccc3a9d97a65@suse.com>


> On 20.05.2024 08:22, Cui, Lili wrote:
> > --- a/gas/config/tc-i386.c
> > +++ b/gas/config/tc-i386.c
> > @@ -4303,22 +4303,20 @@ static void establish_rex (void)
> >    /* Respect a user-specified REX prefix.  */
> >    i.rex |= i.prefix[REX_PREFIX] & REX_OPCODE;
> >
> > -  /* For 8 bit registers we need an empty rex prefix.  Also if the
> > -     instruction already has a prefix, we need to convert old
> > -     registers to new ones.  */
> > -
> > -  if ((i.types[first].bitfield.class == Reg && i.types[first].bitfield.byte
> > -       && ((i.op[first].regs->reg_flags & RegRex64) != 0 || i.rex != 0
> > -	   || i.rex2 != 0))
> > -      || (i.types[last].bitfield.class == Reg && i.types[last].bitfield.byte
> > -	  && ((i.op[last].regs->reg_flags & RegRex64) != 0 || i.rex != 0
> > -	      || i.rex2 != 0)))
> > -    {
> > -      unsigned int x;
> > -
> > -      if (!is_apx_rex2_encoding () && !is_any_vex_encoding(&i.tm))
> > -	i.rex |= REX_OPCODE;
> > -      for (x = first; x <= last; x++)
> > +  /* For 8 bit registers without a prefix, we need an empty rex
> > + prefix.  */
> 
> As you're touching this comment, can you please also correct it? It's not all 8-
> bit registers which are affected here (as expressed by the
> RegRex64 checks).
> 
Done.

> > +  if (((i.types[first].bitfield.class == Reg && i.types[first].bitfield.byte
> > +	&& ((i.op[first].regs->reg_flags & RegRex64) != 0 ))
> 
> Nit: Please parenthesize this line and ...
> 
> > +       || (i.types[last].bitfield.class == Reg && i.types[last].bitfield.byte
> > +	   && (i.op[last].regs->reg_flags & RegRex64) != 0 ))
> 
> ... this one the same way, preferably like the latter. Also please omit the blanks
> before the closing parentheses.
> 
Done.

> > +      && !is_apx_rex2_encoding () && !is_any_vex_encoding (&i.tm) &&
> > + !i.rex)
> 
> Is the !i.rex part needed? It wasn't there before. If it's needed, it would imo
> better come ahead of the APX/VEX checks.
> 
Yes, I added it because there is already i.rex and we don't need to overwrite it. And I will put it ahead of the APX/VEX checks.

> > +    i.rex |= REX_OPCODE;
> > +
> > +  /* For REX/REX2 prefix instructions, we need to convert old registers
> > +     (AL, CL, DL and BL) to new ones (AXL, CXL, DXL and BXL) and report bad
> > +     for AH, CH, DH and BH.  */
> 
> "report bad for" is a little odd; how about simply "reject"?
> 
Done.

> Okay with respective adjustments.

Thanks,
Lili.

  reply	other threads:[~2024-05-22  1:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20  6:21 [PATCH 0/3] Support APX zero-upper Cui, Lili
2024-05-20  6:22 ` [PATCH 1/3] x86: Split REX/REX2 old registers judgment Cui, Lili
2024-05-21 12:18   ` Jan Beulich
2024-05-22  1:33     ` Cui, Lili [this message]
2024-05-22  5:49       ` Jan Beulich
2024-05-22  6:11         ` Cui, Lili
2024-05-22  6:22           ` Jan Beulich
2024-05-20  6:22 ` [PATCH 2/3] Add check for 8-bit old registers in EVEX format Cui, Lili
2024-05-21 12:24   ` Jan Beulich
2024-05-22  2:20     ` Cui, Lili
2024-05-20  6:22 ` [PATCH 3/3] Support APX zero-upper Cui, Lili
2024-05-22  6:21   ` Jan Beulich
2024-05-22  8:05     ` 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=SJ0PR11MB560068F18F93981C894C0E829EEB2@SJ0PR11MB5600.namprd11.prod.outlook.com \
    --to=lili.cui@intel.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.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).