From 39e0f45682a39e09ab115333c593dbdd25658dd2 Mon Sep 17 00:00:00 2001 From: Jan Beulich Date: Mon, 6 Jul 2020 13:35:38 +0200 Subject: x86: replace EXqScalarS by EXqVexScalarS MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There's only a single user, that that one can do fine with the alternative, as the "Vex" aspect of the other operand kind is meaningful only on 3-operand insns. While doing this I noticed that I didn't need to do the same adjustment in the EVEX tables, and voilà - there was a bug, which gets fixed at the same time (see the testsuite changes). --- opcodes/i386-dis.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'opcodes/i386-dis.c') diff --git a/opcodes/i386-dis.c b/opcodes/i386-dis.c index 9147c37..8ef1aa7 100644 --- a/opcodes/i386-dis.c +++ b/opcodes/i386-dis.c @@ -386,7 +386,6 @@ fetch_data (struct disassemble_info *info, bfd_byte *addr) #define EXd { OP_EX, d_mode } #define EXdS { OP_EX, d_swap_mode } #define EXq { OP_EX, q_mode } -#define EXqScalarS { OP_EX, q_scalar_swap_mode } #define EXqS { OP_EX, q_swap_mode } #define EXx { OP_EX, x_mode } #define EXxS { OP_EX, x_swap_mode } @@ -9498,7 +9497,7 @@ static const struct dis386 vex_len_table[][2] = { /* VEX_LEN_0FD6_P_2 */ { - { "vmovq", { EXqScalarS, XMScalar }, 0 }, + { "vmovq", { EXqVexScalarS, XMScalar }, 0 }, }, /* VEX_LEN_0FF7_P_2 */ -- cgit v1.1