aboutsummaryrefslogtreecommitdiff
path: root/COPYING.LIB
diff options
context:
space:
mode:
authorVictor Do Nascimento <victor.donascimento@arm.com>2024-01-05 17:26:09 +0000
committerVictor Do Nascimento <victor.donascimento@arm.com>2024-01-15 13:11:48 +0000
commit51bb8593e6f533970385ca64f40a5bbfc82285da (patch)
tree4f3c00dfd49d72c17c344221c2cff2accdf1d31e /COPYING.LIB
parentc35460087723932ba7300072099bd0d65d9ce6d2 (diff)
downloadgdb-51bb8593e6f533970385ca64f40a5bbfc82285da.zip
gdb-51bb8593e6f533970385ca64f40a5bbfc82285da.tar.gz
gdb-51bb8593e6f533970385ca64f40a5bbfc82285da.tar.bz2
aarch64: rcpc3: New RCPC3_ADDR operand types
The particular choices of address indexing, along with their encoding for RCPC3 instructions lead to the requirement of a new set of operand descriptions, along with the relevant inserter/extractor set. That is, for the integer load/stores, there is only a single valid indexing offset quantity and offset mode is allowed - The value is always equivalent to the amount of data read/stored by the operation and the offset is post-indexed for Load-Acquire RCpc, and pre-indexed with writeback for Store-Release insns. This indexing quantity/mode pair is selected by the setting of a single bit in the instruction. To represent these insns, we add the following operand types: - AARCH64_OPND_RCPC3_ADDR_OPT_POSTIND - AARCH64_OPND_RCPC3_ADDR_OPT_PREIND_WB In the case of loads and stores involving SIMD/FP registers, the optional offset is encoded as an 8-bit signed immediate, but neither post-indexing or pre-indexing with writeback is available. This created the need for an operand type similar to AARCH64_OPND_ADDR_OFFSET, with the difference that FLD_index should not be checked. We thus introduce the AARCH64_OPND_RCPC3_ADDR_OFFSET operand, a variant of AARCH64_OPND_ADDR_OFFSET, w/o the FLD_index bitfield.
Diffstat (limited to 'COPYING.LIB')
0 files changed, 0 insertions, 0 deletions