x86: re-work AVX-VNNI support
authorJan Beulich <jbeulich@suse.com>
Thu, 20 Oct 2022 08:01:12 +0000 (10:01 +0200)
committerJan Beulich <jbeulich@suse.com>
Thu, 20 Oct 2022 08:01:12 +0000 (10:01 +0200)
commit837e225ba1992f9745e5bbbd5e8443243a7f475f
treea540ffd72839917cfbc5b8580c1dfc85904bcd2b
parent15ede33bfa86fd2dfd2d088e01ac2d20cdba46c9
x86: re-work AVX-VNNI support

By putting the templates after their AVX512 counterparts, the AVX512
flavors will be picked by default. That way the need to always use {vex}
ceases to exist once respective CPU features (AVX512-VNNI or AVX512VL as
a whole) have been disabled. This way the need for the PseudoVexPrefix
attribute also disappears.
gas/config/tc-i386.c
gas/testsuite/gas/i386/avx-vnni-inval.l
gas/testsuite/gas/i386/avx-vnni-inval.s
gas/testsuite/gas/i386/avx-vnni.d
gas/testsuite/gas/i386/avx-vnni.s
gas/testsuite/gas/i386/x86-64-avx-vnni-inval.l
gas/testsuite/gas/i386/x86-64-avx-vnni-inval.s
opcodes/i386-gen.c
opcodes/i386-opc.h
opcodes/i386-opc.tbl
opcodes/i386-tbl.h