maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/i386-got-and-copy.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

27 lines
889 B
ArmAsm
Raw Normal View History

[ELF] Do not skip relocation scanning checking if the symbol gets dynamic COPY relocation already It is possible that the same symbol referenced by two kinds of relocations at the same time. The first type requires say GOT entry creation, the second type requires dynamic copy relocation. For MIPS targets they might be R_MIPS_GOT16 and R_MIPS_HI16 relocations. For X86 target they might be R_386_GOT32 and R_386_32 respectively. Now LLD never creates GOT entry for a symbol if this symbol already has related copy relocation. This patch solves this problem. Differential Revision: http://reviews.llvm.org/D18862 llvm-svn: 265910
2016-04-11 05:48:55 +08:00
# REQUIRES: x86
# If there are two relocations such that the first one requires
# dynamic COPY relocation, the second one requires GOT entry
# creation, linker should create both - dynamic relocation
# and GOT entry.
# RUN: llvm-mc -filetype=obj -triple=i386-pc-linux \
# RUN: %S/Inputs/copy-in-shared.s -o %t.so.o
# RUN: llvm-mc -filetype=obj -triple=i386-pc-linux %s -o %t.o
# RUN: ld.lld %t.so.o -shared -o %t.so
[ELF] - Do --hash-style=both by default. Its PR34712, GNU linkers recently changed default values to "both" of "sysv". Patch do the same for all targets except MIPS, where .gnu.hash section is not yet supported. Code suggested by Rui Ueyama. Differential revision: https://reviews.llvm.org/D38407 llvm-svn: 315051
2017-10-06 17:37:44 +08:00
# RUN: ld.lld --hash-style=sysv %t.o %t.so -o %t.exe
[ELF] Do not skip relocation scanning checking if the symbol gets dynamic COPY relocation already It is possible that the same symbol referenced by two kinds of relocations at the same time. The first type requires say GOT entry creation, the second type requires dynamic copy relocation. For MIPS targets they might be R_MIPS_GOT16 and R_MIPS_HI16 relocations. For X86 target they might be R_386_GOT32 and R_386_32 respectively. Now LLD never creates GOT entry for a symbol if this symbol already has related copy relocation. This patch solves this problem. Differential Revision: http://reviews.llvm.org/D18862 llvm-svn: 265910
2016-04-11 05:48:55 +08:00
# RUN: llvm-readobj -r %t.exe | FileCheck %s
# CHECK: Relocations [
# CHECK-NEXT: Section (4) .rel.dyn {
Revert "[ELF] -z combreloc: sort dynamic relocations by (symbol_index,r_offset)" This reverts commit r361125. This linker change breaks shared libraries in some subtle way on x86_64. (Specifically, gold segfaults when loading the LLVMgold.so plugin linked with lldb with this patch.) llvm-svn: 361150
2019-05-20 21:05:55 +08:00
# CHECK-NEXT: 0x{{[0-9A-F]+}} R_386_GLOB_DAT foo
[ELF] -z combreloc: sort dynamic relocations by (!is_relative,symbol_index,r_offset) We currently sort dynamic relocations by (!is_relative,symbol_index). Add r_offset as the third key. This makes `readelf -r` debugging easier (relocations to the same symbol are ordered by r_offset). Refactor the test combreloc.s (renamed from combrelocs.s) to check R_X86_64_RELATIVE, and delete --expand-relocs. The difference from the reverted D61477 is that we keep !is_relative as the first key. In local dynamic TLS model, DTPMOD (e.g. R_ARM_TLS_DTPMOD32 R_X86_64_DTPMOD and R_PPC{,64}_DTPMOD) may use 0 as the symbol index. Reviewed By: grimar Differential Revision: https://reviews.llvm.org/D62141 llvm-svn: 361164
2019-05-20 23:25:01 +08:00
# CHECK-NEXT: 0x{{[0-9A-F]+}} R_386_COPY foo
[ELF] Do not skip relocation scanning checking if the symbol gets dynamic COPY relocation already It is possible that the same symbol referenced by two kinds of relocations at the same time. The first type requires say GOT entry creation, the second type requires dynamic copy relocation. For MIPS targets they might be R_MIPS_GOT16 and R_MIPS_HI16 relocations. For X86 target they might be R_386_GOT32 and R_386_32 respectively. Now LLD never creates GOT entry for a symbol if this symbol already has related copy relocation. This patch solves this problem. Differential Revision: http://reviews.llvm.org/D18862 llvm-svn: 265910
2016-04-11 05:48:55 +08:00
# CHECK-NEXT: }
# CHECK-NEXT: ]
.text
.global _start
_start:
movl $foo, (%esp) # R_386_32 - requires R_386_COPY relocation
movl foo@GOT, %eax # R_386_GOT32 - requires GOT entry