aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineInstr.cpp
diff options
context:
space:
mode:
authorOliver Stannard <oliver.stannard@linaro.org>2021-03-02 13:49:14 +0000
committerOliver Stannard <oliver.stannard@linaro.org>2021-03-04 11:15:57 +0000
commitaac056c528cf139e6881211ee7fe6743c79a68d4 (patch)
tree81f42554a5e4bec621cd21ffce9acd07aaa6da13 /llvm/lib/CodeGen/MachineInstr.cpp
parentd791695cb5172b527e1b0717458d8852abcf34d1 (diff)
downloadllvm-aac056c528cf139e6881211ee7fe6743c79a68d4.zip
llvm-aac056c528cf139e6881211ee7fe6743c79a68d4.tar.gz
llvm-aac056c528cf139e6881211ee7fe6743c79a68d4.tar.bz2
[objdump][ARM] Use correct offset when printing ARM/Thumb branch targets
llvm-objdump only uses one MCInstrAnalysis object, so if ARM and Thumb code is mixed in one object, or if an object is disassembled without explicitly setting the triple to match the ISA used, then branch and call targets will be printed incorrectly. This could be fixed by creating two MCInstrAnalysis objects in llvm-objdump, like we currently do for SubtargetInfo. However, I don't think there's any reason we need two separate sub-classes of MCInstrAnalysis, so instead these can be merged into one, and the ISA determined by checking the opcode of the instruction. Differential revision: https://reviews.llvm.org/D97766
Diffstat (limited to 'llvm/lib/CodeGen/MachineInstr.cpp')
0 files changed, 0 insertions, 0 deletions