mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 19:23:23 +01:00
6979d48fa4
This is a basic first step towards symbolization of disassembled instructions. This used to be done using externally provided (C API) callbacks. This patch introduces: - the MCSymbolizer class, that mimics the same functions that were used in the X86 and ARM disassemblers to symbolize immediate operands and to annotate loads based off PC (for things like c string literals). - the MCExternalSymbolizer class, which implements the old C API. - the MCRelocationInfo class, which provides a way for targets to translate relocations (either object::RelocationRef, or disassembler C API VariantKinds) to MCExprs. - the MCObjectSymbolizer class, which does symbolization using what it finds in an object::ObjectFile. This makes simple symbolization (with no fancy relocation stuff) work for all object formats! - x86-64 Mach-O and ELF MCRelocationInfos. - A basic ARM Mach-O MCRelocationInfo, that provides just enough to support the C API VariantKinds. Most of what works in otool (the only user of the old symbolization API that I know of) for x86-64 symbolic disassembly (-tvV) works, namely: - symbol references: call _foo; jmp 15 <_foo+50> - relocations: call _foo-_bar; call _foo-4 - __cf?string: leaq 193(%rip), %rax ## literal pool for "hello" Stub support is the main missing part (because libObject doesn't know, among other things, about mach-o indirect symbols). As for the MCSymbolizer API, instead of relying on the disassemblers to call the tryAdding* methods, maybe this could be done automagically using InstrInfo? For instance, even though PC-relative LEAs are used to get the address of string literals in a typical Mach-O file, a MOV would be used in an ELF file. And right now, the explicit symbolization only recognizes PC-relative LEAs. InstrInfo should have already have most of what is needed to know what to symbolize, so this can definitely be improved. I'd also like to remove object::RelocationRef::getValueString (it seems only used by relocation printing in objdump), as simply printing the created MCExpr is definitely enough (and cleaner than string concats). llvm-svn: 182625
31 lines
2.0 KiB
Plaintext
31 lines
2.0 KiB
Plaintext
RUN: llvm-objdump -d -symbolize %p/../Inputs/trivial-object-test.elf-x86-64 \
|
|
RUN: | FileCheck %s -check-prefix ELF-x86-64
|
|
RUN: llvm-objdump -d -symbolize %p/../Inputs/trivial-object-test.macho-x86-64 \
|
|
RUN: | FileCheck %s -check-prefix MACHO-x86-64
|
|
|
|
ELF-x86-64: file format ELF64-x86-64
|
|
ELF-x86-64: Disassembly of section .text:
|
|
ELF-x86-64: main:
|
|
ELF-x86-64: 0: 48 83 ec 08 subq $8, %rsp
|
|
ELF-x86-64: 4: c7 44 24 04 00 00 00 00 movl $0, 4(%rsp)
|
|
ELF-x86-64: c: bf 00 00 00 00 movl $.rodata.str1.1, %edi
|
|
ELF-x86-64: 11: e8 00 00 00 00 callq puts-4
|
|
ELF-x86-64: 16: 30 c0 xorb %al, %al
|
|
ELF-x86-64: 18: e8 00 00 00 00 callq SomeOtherFunction-4
|
|
ELF-x86-64: 1d: 8b 44 24 04 movl 4(%rsp), %eax
|
|
ELF-x86-64: 21: 48 83 c4 08 addq $8, %rsp
|
|
ELF-x86-64: 25: c3 ret
|
|
|
|
MACHO-x86-64: file format Mach-O 64-bit x86-64
|
|
MACHO-x86-64: Disassembly of section __TEXT,__text:
|
|
MACHO-x86-64: _main:
|
|
MACHO-x86-64: 0: 48 83 ec 08 subq $8, %rsp
|
|
MACHO-x86-64: 4: c7 44 24 04 00 00 00 00 movl $0, 4(%rsp)
|
|
MACHO-x86-64: c: 48 8d 3d 00 00 00 00 leaq L_.str(%rip), %rdi ## literal pool for: Hello World!
|
|
MACHO-x86-64: 13: e8 00 00 00 00 callq _puts
|
|
MACHO-x86-64: 18: 30 c0 xorb %al, %al
|
|
MACHO-x86-64: 1a: e8 00 00 00 00 callq _SomeOtherFunction
|
|
MACHO-x86-64: 1f: 8b 44 24 04 movl 4(%rsp), %eax
|
|
MACHO-x86-64: 23: 48 83 c4 08 addq $8, %rsp
|
|
MACHO-x86-64: 27: c3 ret
|