diff options
author | Richard Sandiford <richard.sandiford@arm.com> | 2023-03-30 11:09:02 +0100 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@arm.com> | 2023-03-30 11:09:02 +0100 |
commit | eee2ecccdaa37d6c5d283d6346f70897ba27166b (patch) | |
tree | ec16043f0edcdd0b02104b064b4a9b75773ccc9e /sim | |
parent | 89f55b440abdffea9046e225918b5ceb6a57ab85 (diff) | |
download | gdb-eee2ecccdaa37d6c5d283d6346f70897ba27166b.zip gdb-eee2ecccdaa37d6c5d283d6346f70897ba27166b.tar.gz gdb-eee2ecccdaa37d6c5d283d6346f70897ba27166b.tar.bz2 |
aarch64: Fix SVE2 register/immediate distinction
GAS refuses to interpret register names like x0 as unadorned
immediates, due to the obvious potential for confusion with
register operands. (An explicit #x0 is OK.)
For compatibility reasons, we can't extend the set of registers
that GAS rejects for existing instructions. For example:
mov x0, z0
was valid code before SVE was added, so it needs to stay valid
code even when SVE is enabled. But we can make GAS reject newer
registers in newer instructions. The SVE instruction:
and z0.s, z0.s, z0.h
is therefore invalid, rather than z0.h being an immediate.
This patch extends the SVE behaviour to SVE2. The old call
to AARCH64_CPU_HAS_FEATURE was technically the wrong way around,
although it didn't matter in practice for base SVE instructions
since their avariants only set SVE.
Diffstat (limited to 'sim')
0 files changed, 0 insertions, 0 deletions