mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-07-20 10:30:03 +00:00
7486d92a6c
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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182908 91177308-0d34-0410-b5e6-96231b3b80d8
21 lines
689 B
ArmAsm
21 lines
689 B
ArmAsm
// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | llvm-readobj -r -t | FileCheck %s
|
|
|
|
// Test that this produces a R_X86_64_GOT32 and that we have an undefined
|
|
// reference to _GLOBAL_OFFSET_TABLE_.
|
|
|
|
movl foo@GOT, %eax
|
|
movl foo@GOTPCREL(%rip), %eax
|
|
|
|
// CHECK: Relocations [
|
|
// CHECK: Section ({{[^ ]+}}) .rela.text {
|
|
// CHECK-NEXT: 0x{{[^ ]+}} R_X86_64_GOT32 foo 0x{{[^ ]+}}
|
|
// CHECK-NEXT: 0x{{[^ ]+}} R_X86_64_GOTPCREL foo 0x{{[^ ]+}}
|
|
// CHECK-NEXT: }
|
|
// CHECK-NEXT: ]
|
|
|
|
// CHECK: Symbol {
|
|
// CHECK: Name: _GLOBAL_OFFSET_TABLE_
|
|
// CHECK-NEXT: Value:
|
|
// CHECK-NEXT: Size:
|
|
// CHECK-NEXT: Binding: Global
|