diff options
author | Craig Topper <craig.topper@sifive.com> | 2020-12-04 10:31:23 -0800 |
---|---|---|
committer | Craig Topper <craig.topper@sifive.com> | 2020-12-04 10:34:12 -0800 |
commit | ad923edfc1ce0c0b60e8270954c8d098aab3c3f8 (patch) | |
tree | cb3ffb94d59616fa2ae7c5b7267a33ba6f7703d9 /llvm/lib/Support/JSON.cpp | |
parent | ca2888310b245d0532d989685a090ae373ee3f93 (diff) | |
download | llvm-ad923edfc1ce0c0b60e8270954c8d098aab3c3f8.zip llvm-ad923edfc1ce0c0b60e8270954c8d098aab3c3f8.tar.gz llvm-ad923edfc1ce0c0b60e8270954c8d098aab3c3f8.tar.bz2 |
[RISCV] Add support for printing pcrel immediates as absolute addresses in llvm-objdump
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
Diffstat (limited to 'llvm/lib/Support/JSON.cpp')
0 files changed, 0 insertions, 0 deletions