diff options
author | Richard Sandiford <richard.sandiford@arm.com> | 2023-03-30 11:09:11 +0100 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@arm.com> | 2023-03-30 11:09:11 +0100 |
commit | e2dc4040f30caba49d2bb7bd1d5119dd8a72cdba (patch) | |
tree | 0cfebab3ae6d8f57a7e9f44c876059922ec076d7 /libdecnumber | |
parent | 90cd80f8c24f9919a10117aa93fc570ac8b7767a (diff) | |
download | gdb-e2dc4040f30caba49d2bb7bd1d5119dd8a72cdba.zip gdb-e2dc4040f30caba49d2bb7bd1d5119dd8a72cdba.tar.gz gdb-e2dc4040f30caba49d2bb7bd1d5119dd8a72cdba.tar.bz2 |
aarch64: Add support for vgx2 and vgx4
Many SME2 instructions operate on groups of 2 or 4 ZA vectors.
This is indicated by adding a "vgx2" or "vgx4" group size to the
ZA index. The group size is optional in assembly but preferred
for disassembly.
There is not a binary distinction between mnemonics that have
group sizes and mnemonics that don't, nor between mnemonics that
take vgx2 and mnemonics that take vgx4. We therefore get better
error messages if we allow any ZA index to have a group size
during parsing, and wait until constraint checking to reject
invalid sizes.
A quirk of the way errors are reported means that if an instruction
is wrong both in its qualifiers and its use of a group size, we'll
print suggested alternative instructions that also have an incorrect
group size. But that's a general property that also applies to
things like out-of-range immediates. It's also not obviously the
wrong thing to do. We need to be relatively confident that we're
looking at the right opcode before reporting detailed operand-specific
errors, so doing qualifier checking first seems resonable.
Diffstat (limited to 'libdecnumber')
0 files changed, 0 insertions, 0 deletions