From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: improve/shorten vector zeroing-idiom optimization conditional
Date: Tue, 2 Aug 2022 08:56:47 -0700 [thread overview]
Message-ID: <CAMe9rOrPEJSrV9B7qhnqUL+fBzMe=r1915nW7wWKu7uS1neK4g@mail.gmail.com> (raw)
In-Reply-To: <d72e0efe-9918-d6ed-65fa-92c6d5ee08dd@suse.com>
On Tue, Aug 2, 2022 at 8:20 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> - Drop the rounding type check: We're past template matching, and none
> of the involved insns support embedded rounding.
> - Drop the extension opcode check: None of the involved opcodes have
> variants with it being other than None.
> - Instead check opcode space, even if just to be on the safe side going
> forward.
> - Reduce the number of comparisons by folding two groups.
>
> --- a/gas/config/tc-i386.c
> +++ b/gas/config/tc-i386.c
> @@ -4329,24 +4329,19 @@ optimize_encoding (void)
> && !i.types[2].bitfield.xmmword
> && (i.tm.opcode_modifier.vex
> || ((!i.mask.reg || i.mask.zeroing)
> - && i.rounding.type == rc_none
> && is_evex_encoding (&i.tm)
> && (i.vec_encoding != vex_encoding_evex
> || cpu_arch_isa_flags.bitfield.cpuavx512vl
> || i.tm.cpu_flags.bitfield.cpuavx512vl
> || (i.tm.operand_types[2].bitfield.zmmword
> && i.types[2].bitfield.ymmword))))
> - && ((i.tm.base_opcode == 0x55
> - || i.tm.base_opcode == 0x57
> - || i.tm.base_opcode == 0xdf
> - || i.tm.base_opcode == 0xef
> - || i.tm.base_opcode == 0xf8
> - || i.tm.base_opcode == 0xf9
> - || i.tm.base_opcode == 0xfa
> - || i.tm.base_opcode == 0xfb
> - || i.tm.base_opcode == 0x42
> - || i.tm.base_opcode == 0x47)
> - && i.tm.extension_opcode == None))
> + && i.tm.opcode_modifier.opcodespace == SPACE_0F
> + && ((i.tm.base_opcode | 2) == 0x57
> + || i.tm.base_opcode == 0xdf
> + || i.tm.base_opcode == 0xef
> + || (i.tm.base_opcode | 3) == 0xfb
> + || i.tm.base_opcode == 0x42
> + || i.tm.base_opcode == 0x47))
> {
> /* Optimize: -O1:
> VOP, one of vandnps, vandnpd, vxorps, vxorpd, vpsubb, vpsubd,
OK.
Thanks.
--
H.J.
prev parent reply other threads:[~2022-08-02 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 15:20 Jan Beulich
2022-08-02 15:56 ` H.J. Lu [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='CAMe9rOrPEJSrV9B7qhnqUL+fBzMe=r1915nW7wWKu7uS1neK4g@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--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).