fits_in_disp8() can be called before ambiguous operands get resolved
or rejected (in process_suffix()), which requires that i.memshift be
non-negative to avoid an internal error. This case wasn't covered by
6c0946d0d28d ("x86: correct VFPCLASSP{S,D} operand size handling").
i.memshift = t->opcode_modifier.disp8memshift;
else
{
- const i386_operand_type *type = NULL;
+ const i386_operand_type *type = NULL, *fallback = NULL;
i.memshift = 0;
for (op = 0; op < i.operands; op++)
type = &t->operand_types[op];
else if (!i.types[op].bitfield.unspecified)
type = &i.types[op];
+ else /* Ambiguities get resolved elsewhere. */
+ fallback = &t->operand_types[op];
}
else if (i.types[op].bitfield.class == RegSIMD
&& t->opcode_modifier.evex != EVEXLIG)
i.memshift = 4;
}
+ if (!type && !i.memshift)
+ type = fallback;
if (type)
{
if (type->bitfield.zmmword)
vcvtuqq2ps xmm0, [rax]
vfpclasspd k0, [eax], 0
- vfpclassps k0, [eax], 0
+ vfpclassps k0, [eax+1], 0
.att_syntax prefix
[ ]*[1-9][0-9]*[ ]+\.intel_syntax noprefix
[ ]*[1-9][0-9]*[ ]+\?\?\?\? 62F3FD48 vfpclasspd k0, \[eax], 0
[ ]*[1-9][0-9]*[ ]+660000
-[ ]*[1-9][0-9]*[ ]+\?\?\?\? 62F37D48 vfpclassps k0, \[eax], 0
-[ ]*[1-9][0-9]*[ ]+660000
+[ ]*[1-9][0-9]*[ ]+\?\?\?\? 62F37D48 vfpclassps k0, \[eax\+0x80], 0
+[ ]*[1-9][0-9]*[ ]+66400200 ?
[ ]*[1-9][0-9]*[ ]+
#pass
.intel_syntax noprefix
vfpclasspd k0, [eax], 0
- vfpclassps k0, [eax], 0
+ vfpclassps k0, [eax+0x80], 0
.p2align 4