mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-26 12:43:36 +01:00
218109597e
This makes the llvm-objdump output much more readable and closer to binutils objdump. This builds on D76591 It requires changing the OperandType for certain immediates to "OPERAND_PCREL" so tablegen will generate code to pass the instruction's address. This means we can't do the generic check on these instructions in verifyInstruction any more. Should I add it back with explicit opcode checks? Or should we add a new operand flag to control the passing of address instead of matching the name? Differential Revision: https://reviews.llvm.org/D92147
20 lines
849 B
ArmAsm
20 lines
849 B
ArmAsm
# RUN: llvm-mc -triple riscv32 -mattr=+c -show-encoding < %s \
|
|
# RUN: | FileCheck -check-prefixes=CHECK,CHECK-ALIAS %s
|
|
# RUN: llvm-mc -triple riscv32 -mattr=+c -show-encoding \
|
|
# RUN: -riscv-no-aliases <%s | FileCheck -check-prefixes=CHECK,CHECK-INST %s
|
|
# RUN: llvm-mc -triple riscv32 -mattr=+c -filetype=obj < %s \
|
|
# RUN: | llvm-objdump --triple=riscv32 --mattr=+c -d - \
|
|
# RUN: | FileCheck -check-prefixes=CHECK-BYTES,CHECK-ALIASOBJ %s
|
|
# RUN: llvm-mc -triple riscv32 -mattr=+c -filetype=obj < %s \
|
|
# RUN: | llvm-objdump --triple=riscv32 --mattr=+c -d -M no-aliases - \
|
|
# RUN: | FileCheck -check-prefixes=CHECK-BYTES,CHECK-INSTOBJ %s
|
|
|
|
# c.jal is an rv32 only instruction.
|
|
jal ra, 2046
|
|
# CHECK-BYTES: fd 2f
|
|
# CHECK-ALIASOBJ: jal 0x7fe
|
|
# CHECK-ALIAS: jal 2046
|
|
# CHECK-INST: c.jal 2046
|
|
# CHECK-INSTOBJ: c.jal 0x7fe
|
|
# CHECK: # encoding: [0xfd,0x2f]
|