x86: reuse further VEX entries for EVEX
authorJan Beulich <jbeulich@suse.com>
Wed, 10 Mar 2021 07:19:11 +0000 (08:19 +0100)
committerJan Beulich <jbeulich@suse.com>
Wed, 10 Mar 2021 07:19:11 +0000 (08:19 +0100)
commit85ba7507f695f914d0ad22b6d1c60bc3571f5345
tree9de6b0b4de79c378ee0d1dafd1870532d806e9db
parent066f82b96a4902b9f4f76dfc8d24f8d73ceeef0f
x86: reuse further VEX entries for EVEX

When the VEX.L=1 decode matches that of both EVEX.L'L=1 and EVEX.L'L=2
(typically when all three are invalid) the (smaller) VEX table entry can
be reused by EVEX, instead of duplicating data. (Note that XM and XMM as
well as EXxmm_md and EXd are equivalent at least for the purposes here.)
opcodes/ChangeLog
opcodes/i386-dis-evex-len.h
opcodes/i386-dis-evex-prefix.h
opcodes/i386-dis-evex-w.h
opcodes/i386-dis-evex.h
opcodes/i386-dis.c
This page took 0.027772 seconds and 4 git commands to generate.