x86-64: don't hide an empty but meaningless REX prefix
authorJan Beulich <jbeulich@suse.com>
Tue, 14 Jul 2020 08:24:26 +0000 (10:24 +0200)
committerJan Beulich <jbeulich@suse.com>
Tue, 14 Jul 2020 08:24:26 +0000 (10:24 +0200)
commite184e6110e2836bb0ec712e380dbcac402fe4056
tree93fc77dc46849ff3754484d0bcafd453d2c5af3f
parente8b5d5f9713b7c74f95c4ff573ddeb7ebdb3fbc3
x86-64: don't hide an empty but meaningless REX prefix

Unlike for non-zero values passed to USED_REX(), where rex_used gets
updated only when the respective bit was actually set in the encoding,
zero getting passed in is not further guarded, yet such a (potentially
"empty") REX prefix takes effect only when there are registers numbered
4 and up.
gas/ChangeLog
gas/testsuite/gas/i386/x86-64-pseudos.d
gas/testsuite/gas/i386/x86-64-pseudos.s
gas/testsuite/gas/i386/x86-64-reg-intel.d
gas/testsuite/gas/i386/x86-64-reg.d
opcodes/ChangeLog
opcodes/i386-dis.c