aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorAlice Carlotti <alice.carlotti@arm.com>2025-07-11 12:41:51 +0100
committerAlice Carlotti <alice.carlotti@arm.com>2025-07-12 10:04:27 +0100
commit8f788f9464353f4fae79f007f6ab3a0095bd1c9a (patch)
tree148fcd5af056fe9a2270beb99976162d7ce4b177 /gdb/python/python.c
parent891fa528c2b3c8aac3e959ec6496ebffe5e5db15 (diff)
downloadbinutils-8f788f9464353f4fae79f007f6ab3a0095bd1c9a.zip
binutils-8f788f9464353f4fae79f007f6ab3a0095bd1c9a.tar.gz
binutils-8f788f9464353f4fae79f007f6ab3a0095bd1c9a.tar.bz2
aarch64: Use operand class to select movprfx error
Previously the choice of error message for an invalid movprfx sequence used the architecture requirements to determine whether an instruction was an SVE instruction or not. This meant specifying SVE or SVE2 as an explicit architecture requirement for all SVE instructions, even when this was already implied by another feature. As more architecture features are added and with the partial removal of the SME->SVE2 dependency, these extra feature requirements were getting messier and easier to forget. Instead, we now look at the operand types. If there is an SVE_REG, SVE_REGLIST or PRED_REG operand, then we treat the instruction as an SVE instruction. This does change behaviour slightly, but it only affects the choice of error message and the new choice should be a bit more consistent. There is one testsuite update required, because Ezra's SVE_AES2 patch temporarily broke classification of FEAT_SVE_AES instructions. This patch restores the original behaviour.
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions