llvm-project/llvm/test/MC/ELF/weak-relocation.s

// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | llvm-readobj -r | FileCheck %s

// Test that weak symbols always produce relocations

	.weak	foo
foo:
bar:
        call    foo

// CHECK:      Relocations [
// CHECK-NEXT:   Section ({{[0-9]+}}) .rela.text {
// CHECK-NEXT:     0x1 R_X86_64_PLT32 foo 0xFFFFFFFFFFFFFFFC
// CHECK-NEXT:   }
// CHECK-NEXT: ]
Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \| llvm-readobj -r \| FileCheck %s`
PR9352: Always emit a relocation for weak symbols. Not emitting relocations for calls to weak symbols with a definition has the appearance of working with LLVM-generated code because weak symbol definitions are put in their own sections. llvm-svn: 126933 2011-03-03 15:24:36 +08:00
			`// Test that weak symbols always produce relocations`

			`.weak foo`
			`foo:`
			`bar:`
			`call foo`

Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// CHECK: Relocations [`
Change how we iterate over relocations on ELF. 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 2013-05-30 11:05:14 +08:00			`// CHECK-NEXT: Section ({{[0-9]+}}) .rela.text {`
[llvm-mc] - Produce R_X86_64_PLT32 for "call/jmp foo". For instructions like call foo and jmp foo patch changes relocation produced from R_X86_64_PC32 to R_X86_64_PLT32. Relocation can be used as a marker for 32-bit PC-relative branches. Linker will reduce PLT32 relocation to PC32 if function is defined locally. Differential revision: https://reviews.llvm.org/D43383 llvm-svn: 325569 2018-02-20 18:17:57 +08:00			`// CHECK-NEXT: 0x1 R_X86_64_PLT32 foo 0xFFFFFFFFFFFFFFFC`
Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// CHECK-NEXT: }`
			`// CHECK-NEXT: ]`