diff options
| author | Ilya Leoshkevich <iii@linux.ibm.com> | 2023-07-20 10:11:24 +0200 |
|---|---|---|
| committer | Ilya Leoshkevich <iii@linux.ibm.com> | 2023-07-21 11:09:19 +0200 |
| commit | a0eee6c971878b1f2edcc34fb2513e12a04a29ba (patch) | |
| tree | 04e5c801545c229b2b881acc771619bde8acf9b0 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | e6c62a2dcc8c12df2c94397e9f4537f45e32f230 (diff) | |
[SystemZ] Allow symbols in immediate asm operands
Currently mentioning any symbols in immediate asm operands is not
supported, for example:
error: invalid operand for instruction
lghi %r4,foo_end-foo
The immediate problem is that is*Imm() and print*Operand() functions do
not accept MCExprs, but simply relaxing these checks is not enough:
after symbol addresses are computed, range checks need to run against
resolved values.
Add a number of SystemZ::FixupKind members for each kind of immediate
value and process them in SystemZMCAsmBackend::applyFixup(). Only
perform the range checks, do not change anything.
Adjust the tests: move previously failing cases like the one shown
above out of insn-bad.s.
Reviewed By: uweigand
Differential Revision: https://reviews.llvm.org/D154899
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions
