public inbox for binutils-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@sourceware.org> To: bfd-cvs@sourceware.org Subject: [binutils-gdb] x86: improve/shorten vector zeroing-idiom optimization conditional Date: Wed, 3 Aug 2022 07:01:30 +0000 (GMT) [thread overview] Message-ID: <20220803070130.3F9203851157@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5844ccaac7d7e628b8c3feea725d87fd4bafbdf6 commit 5844ccaac7d7e628b8c3feea725d87fd4bafbdf6 Author: Jan Beulich <jbeulich@suse.com> Date: Wed Aug 3 09:01:10 2022 +0200 x86: improve/shorten vector zeroing-idiom optimization conditional - 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. Diff: --- gas/config/tc-i386.c | 19 +++++++------------ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git a/gas/config/tc-i386.c b/gas/config/tc-i386.c index 78dad4ebdf1..62d583be47c 100644 --- 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,
reply other threads:[~2022-08-03 7:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220803070130.3F9203851157@sourceware.org \ --to=jbeulich@sourceware.org \ --cc=bfd-cvs@sourceware.org \ /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: linkBe 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).