maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/ELF/x86_64-reloc-sizetest.s

14 lines
415 B
ArmAsm
Raw Normal View History

Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361
2013-04-12 12:06:46 +08:00
// RUN: llvm-mc -triple x86_64-linux-gnu -filetype=obj %s | llvm-readobj -r | FileCheck %s
Fix http://llvm.org/bugs/show_bug.cgi?id=10568 Move the reloc size assert into AsmBackend - where it is more apropos. llvm-svn: 136855
2011-08-04 08:38:45 +08:00
// Tests that relocation value fits in the provided size
// Original bug http://llvm.org/bugs/show_bug.cgi?id=10568
Print all the bits in the addend. llvm-svn: 136867
2011-08-04 21:00:24 +08:00
Fix http://llvm.org/bugs/show_bug.cgi?id=10568 Move the reloc size assert into AsmBackend - where it is more apropos. llvm-svn: 136855
2011-08-04 08:38:45 +08:00
L: movq $(L + 2147483648),%rax
Print all the bits in the addend. llvm-svn: 136867
2011-08-04 21:00:24 +08:00
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 {
Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361
2013-04-12 12:06:46 +08:00
// CHECK-NEXT: 0x3 R_X86_64_32S {{[^ ]+}} 0x80000000
// CHECK-NEXT: }
// CHECK-NEXT: ]