aac056c528
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 |
||
|---|---|---|
| .. | ||
| AArch64 | ||
| AMDGPU | ||
| ARM | ||
| Hexagon | ||
| Inputs | ||
| Mips | ||
| PowerPC | ||
| RISCV | ||
| call-absolute-symbol.test | ||
| dynamic-section-machine-specific.test | ||
| dynamic-section.test | ||
| file-headers.test | ||
| invalid-phdr.test | ||
| proc-specific-section.test | ||
| pt-gnu-property.test | ||
| relocations.test | ||
| symbol-table.test | ||
| symbol-visibility.test | ||
| verdef.test | ||
| verneed.test | ||