diff options
| author | Jonathan Thackray <jonathan.thackray@arm.com> | 2025-10-08 16:45:51 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-08 16:45:51 +0100 |
| commit | 2690bb6db6ea583d402bb97ea44c5a1ff930ace7 (patch) | |
| tree | 593ec35dce8a76e1e4b91027a05bcda30795455d /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h | |
| parent | 6c4bd66114bc3a284f45112cb2ba57de2aee4f7e (diff) | |
| download | llvm-2690bb6db6ea583d402bb97ea44c5a1ff930ace7.zip llvm-2690bb6db6ea583d402bb97ea44c5a1ff930ace7.tar.gz llvm-2690bb6db6ea583d402bb97ea44c5a1ff930ace7.tar.bz2 | |
[AArch64][llvm] Reject assembler for invalid TLBIP instructions (#162090)
Some invalid assembler is currently allowed for `tlbip` sys alias
instructions, since there's only a single table in tablegen for both
`tlbi` and `tlbip` instructions. However, the latter is only a subset of
the former, so invalid machine code is generated for `tlbip`
instructions which don't actually exist.
Define a `TLBI_and_TLBIP` and `TLBI_only` enum (wish tablegen had first
class enum support), so that only valid `tlbip` instructions are created
in the `TLBIPEntry` table, and instructions which are not valid are
correctly rejected. Add new testcases for this.
(See the Arm ARM DDI 0487 L.b pages C5-802 to 809 where valid `tlbi` and
`tlbip` instructions are defined).
For example, before this change, both of the following are accepted.
Subsequent to this change, `tlbip` is correctly rejected:
```
% llvm-mc -triple=aarch64 <<< "tlbi alle1" --show-encoding
tlbi alle1 // encoding: [0x9f,0x87,0x0c,0xd5]
% llvm-mc -triple=aarch64 -mattr=+d128 <<< "tlbip alle1, x0, x1"
<stdin>:1:7: error: invalid operand for TLBIP instruction
tlbip alle1
^
```
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h')
0 files changed, 0 insertions, 0 deletions
