diff options
| author | Jan Beulich <jbeulich@suse.com> | 2021-03-29 12:04:03 +0200 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2021-03-29 12:04:03 +0200 |
| commit | 73e45eb208585e672945078b28fc8381c6f6ba5f (patch) | |
| tree | ef991416848f48625b0876fc75e8c469f543a947 /gdb/gdb_regex.c | |
| parent | 9df6f676c2c7280dc0c419c43927a07c6359814d (diff) | |
| download | gdb-73e45eb208585e672945078b28fc8381c6f6ba5f.zip gdb-73e45eb208585e672945078b28fc8381c6f6ba5f.tar.gz gdb-73e45eb208585e672945078b28fc8381c6f6ba5f.tar.bz2 | |
x86: undo Prefix_0X<nn> use in opcode table
The table entries are more natural to read (and slightly shorter) when
the prefixes, like is the case for VEX/XOP/EVEX-encoded entries, are
specified as part of the opcode. This is particularly noticable for
side-by-side legacy and SSE2AVX entries.
An implication is that we now need to use "unsigned long long" for the
initially parsed opcode in i386-gen. I don't expect this to be an issue.
Diffstat (limited to 'gdb/gdb_regex.c')
0 files changed, 0 insertions, 0 deletions