llvm-project/lld/test/ELF/relocation-past-merge-end.s

// REQUIRES: x86
// RUN: llvm-mc %s -o %t.o -filetype=obj -triple=x86_64-pc-linux
// RUN: not ld.lld %t.o -o /dev/null -shared 2>&1 | FileCheck %s
// CHECK: relocation-past-merge-end.s.tmp.o:(.foo): offset is outside the section

.data
.quad .foo + 10
.section	.foo,"aM",@progbits,4
.quad 0
Add support for merging the contents of SHF_MERGE sections. For now SHF_STRINGS are not supported. llvm-svn: 250737 2015-10-20 05:00:02 +08:00			`// REQUIRES: x86`
			`// RUN: llvm-mc %s -o %t.o -filetype=obj -triple=x86_64-pc-linux`
[ELF] Replace unused output filenames with /dev/null in tests Post commit review at rLLD335992 llvm-svn: 336129 2018-07-03 01:48:23 +08:00			`// RUN: not ld.lld %t.o -o /dev/null -shared 2>&1 \| FileCheck %s`
[LLD] Check too large offsets into merge sections earlier This patch moves the checking for too large offsets into merge sections earlier. Without this change the large offset generated in the added test-case will cause an assert (as it happens to be a value reserved as a "tombstone" in the DenseMap implementation) when OffsetMap is queried in getSectionPiece(). To simplify the code and avoid future mistakes I have refactored so that there is only one function that looks up offsets in the OffsetMap. Differential Revision: https://reviews.llvm.org/D51180 llvm-svn: 341206 2018-08-31 19:51:51 +08:00			`// CHECK: relocation-past-merge-end.s.tmp.o:(.foo): offset is outside the section`
Add support for merging the contents of SHF_MERGE sections. For now SHF_STRINGS are not supported. llvm-svn: 250737 2015-10-20 05:00:02 +08:00
Do not handle zero-sized mergeable section as mergeable. Mergeable sections with size zero are useless because they don't actually contain data, and therefore there's no merit ot merge them. However, in reality, there are object files in the wild containing such sections. Currently, LLD can't handle them proerply. This patch makes LLD to handle such sections as if they are non- mergeable to fix the issue. Fixes bug 28822. llvm-svn: 277568 2016-08-03 13:28:02 +08:00			`.data`
[ELF] Make the rule to create relative relocations in a writable section stricter The current rule is loose: `!Sym.IsPreemptible \|\| Expr == R_GOT`. When the symbol is non-preemptable, this allows absolute relocation types with smaller numbers of bits, e.g. R_X86_64_{8,16,32}. They are disallowed by ld.bfd and gold, e.g. ld.bfd: a.o: relocation R_X86_64_8 against `.text' can not be used when making a shared object; recompile with -fPIC This patch: a) Add TargetInfo::SymbolicRel to represent relocation types that resolve to a symbol value (e.g. R_AARCH_ABS64, R_386_32, R_X86_64_64). As a side benefit, we currently (ab)use GotRel (R__GLOB_DAT) to resolve GOT slots that are link-time constants. Since we now use Target->SymbolRel to do the job, we can remove R__GLOB_DAT from relocateOne() for all targets. R_*_GLOB_DAT cannot be used as static relocation types. b) Change the condition to `!Sym.IsPreemptible && Type != Target->SymbolicRel \|\| Expr == R_GOT`. Some tests are caught by the improved error checking (ld.bfd/gold also issue errors on them). Many misuse .long where .quad should be used instead. Reviewed By: ruiu Differential Revision: https://reviews.llvm.org/D63121 llvm-svn: 363059 2019-06-11 20:59:30 +08:00			`.quad .foo + 10`
Do not handle zero-sized mergeable section as mergeable. Mergeable sections with size zero are useless because they don't actually contain data, and therefore there's no merit ot merge them. However, in reality, there are object files in the wild containing such sections. Currently, LLD can't handle them proerply. This patch makes LLD to handle such sections as if they are non- mergeable to fix the issue. Fixes bug 28822. llvm-svn: 277568 2016-08-03 13:28:02 +08:00			`.section .foo,"aM",@progbits,4`
			`.quad 0`