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 V4] Support APX NF
Date: Mon, 1 Apr 2024 06:20:56 +0000	[thread overview]
Message-ID: <SJ0PR11MB56001862B6A5A427EC58F1719E3F2@SJ0PR11MB5600.namprd11.prod.outlook.com> (raw)
In-Reply-To: <47e11c46-ae50-4a68-9b09-6f5d5d1d9fe0@suse.com>

> On 26.03.2024 07:49, Cui, Lili wrote:
> > --- a/gas/testsuite/gas/i386/x86-64-apx-inval.s
> > +++ b/gas/testsuite/gas/i386/x86-64-apx-inval.s
> > @@ -2,3 +2,12 @@
> >  	.text
> >  	addq $0xe0, %fs:0, %rdx
> >  	xorq $0xe0, foo(%eax,%edx), %rdx
> > +	{nf} adc $1, (%rax)
> > +	{nf} not %r15
> > +	{nf} rcl $0x7b,%r15
> > +	{nf} rcr $0x7b,%r15
> > +	{nf} sbb $0x7b,%r15
> > +	{nf} pop2 %rax, %rbx
> > +	{nf} push2 %rbx, %rax
> 
> I think it would be nice if one of ADCX/ADOX and at least one of the BMI2
> insns not permitting NF would also be covered here.
> 

Done.

> > --- /dev/null
> > +++ b/gas/testsuite/gas/i386/x86-64-apx-nf-intel.d
> > @@ -0,0 +1,1383 @@
> > +#as:
> > +#objdump: -dw -Mintel
> > +#name: x86_64 APX_F insns (Intel disassembly)
> 
> Here, ...
> 
> > --- /dev/null
> > +++ b/gas/testsuite/gas/i386/x86-64-apx-nf.d
> > @@ -0,0 +1,1383 @@
> > +#as:
> > +#objdump: -dw
> > +#name: x86_64 APX_F insns
> 
> ... here, and ...
> 
> > --- /dev/null
> > +++ b/gas/testsuite/gas/i386/x86-64-apx-nf.s
> > @@ -0,0 +1,1378 @@
> > +# Check 64bit APX_F instructions
> 
> ... in this comment NF wants mentioning.
> 

Done.

> > +	{nf}	blsmsk	%ecx, %edx
> > +	{nf}	blsmsk	%r9, %r31
> > +	{nf}	blsmsk	291(%r8, %rax, 4), %ecx
> > +	{nf}	blsmsk	291(%r8, %rax, 4), %r9
> > +	{nf}	blsr	%ecx, %edx
> > +	{nf}	blsr	%r9, %r31
> > +	{nf}	blsr	291(%r8, %rax, 4), %ecx
> > +	{nf}	blsr	291(%r8, %rax, 4), %r9
> > +	{nf}	bzhi	%ecx, %edx, %r10d
> > +	{nf}	bzhi	%ecx, 291(%r8, %rax, 4), %edx
> > +	{nf}	bzhi	%r9, %r31, %r11
> > +	{nf}	bzhi	%r9, 291(%r8, %rax, 4), %r31
> > +	{nf}	dec	%bl
> 
> No CLR test here? Oh, I see it's at the bottom. I wants moving here.
>
 
Done.

Thanks,
Lili.

      reply	other threads:[~2024-04-01  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  6:49 Cui, Lili
2024-03-28 11:24 ` Jan Beulich
2024-04-01  6:20   ` Cui, Lili [this message]

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=SJ0PR11MB56001862B6A5A427EC58F1719E3F2@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).