These lines are shown in the manual with a weird representation that
confers a special meaning to 0x66 0xF2 prefixes. In reality, this is
just the CRC32 instruction (chosen by 0xF2) plus a data size override
prefix. All other instruction in the range that use the 0xF2 prefix
are VEX-encoded and therefore they do not support multiple prefixes.
Because of this, it is possible to handle the four prefixes normally
using decode_by_prefix; the 0x66 0xF2 combination for CRC32 is handled
naturally by the "v" operand size.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
e45fd081db