mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-31 16:02:52 +01:00
5b34d5a3c7
For COFF and MachO, sections semantically have relocations that apply to them. That is not the case on ELF. In relocatable objects (.o), a section with relocations in ELF has offsets to another section where the relocations should be applied. In dynamic objects and executables, relocations don't have an offset, they have a virtual address. The section sh_info may or may not point to another section, but that is not actually used for resolving the relocations. This patch exposes that in the ObjectFile API. It has the following advantages: * Most (all?) clients can handle this more efficiently. They will normally walk all relocations, so doing an effort to iterate in a particular order doesn't save time. * llvm-readobj now prints relocations in the same way the native readelf does. * probably most important, relocations that don't point to any section are now visible. This is the case of relocations in the rela.dyn section. See the updated relocation-executable.test for example. llvm-svn: 182908
19 lines
770 B
ArmAsm
19 lines
770 B
ArmAsm
// RUN: llvm-mc -triple=aarch64-none-linux-gnu -filetype=obj %s -o - | \
|
|
// RUN: llvm-readobj -r | FileCheck -check-prefix=OBJ %s
|
|
|
|
ldrb w0, [sp, #:lo12:some_label]
|
|
ldrh w0, [sp, #:lo12:some_label]
|
|
ldr w0, [sp, #:lo12:some_label]
|
|
ldr x0, [sp, #:lo12:some_label]
|
|
str q0, [sp, #:lo12:some_label]
|
|
|
|
// OBJ: Relocations [
|
|
// OBJ-NEXT: Section (2) .rela.text {
|
|
// OBJ-NEXT: 0x0 R_AARCH64_LDST8_ABS_LO12_NC some_label 0x0
|
|
// OBJ-NEXT: 0x4 R_AARCH64_LDST16_ABS_LO12_NC some_label 0x0
|
|
// OBJ-NEXT: 0x8 R_AARCH64_LDST32_ABS_LO12_NC some_label 0x0
|
|
// OBJ-NEXT: 0xC R_AARCH64_LDST64_ABS_LO12_NC some_label 0x0
|
|
// OBJ-NEXT: 0x10 R_AARCH64_LDST128_ABS_LO12_NC some_label 0x0
|
|
// OBJ-NEXT: }
|
|
// OBJ-NEXT: ]
|