llvm-mirror/test/tools/gold/alias.ll

; RUN: llvm-as %s -o %t.o
; RUN: llvm-as %p/Inputs/alias-1.ll -o %t2.o
; RUN: ld -shared -o %t3.o -plugin %llvmshlibdir/LLVMgold.so %t2.o %t.o \
; RUN:  -plugin-opt=emit-llvm
; RUN: llvm-dis %t3.o -o - | FileCheck %s

; CHECK: @a = global i32 42
; CHECK: @b = global i32 1

@a = weak alias i32* @b
@b = global i32 1
Rewrite the gold plugin to fix pr19901. There is a fundamental difference between how the gold API and lib/LTO view the LTO process. The gold API talks about a particular symbol in a particular file. The lib/LTO API talks about a symbol in the merged module. The merged module is then defined in terms of the IR semantics. In particular, a linkonce_odr GV is only copied if it is used, since it is valid to drop unused linkonce_odr GVs. In the testcase in pr19901 both properties collide. What happens is that gold asks us to keep a particular linkonce_odr symbol, but the IR linker doesn't copy it to the merged module and we never have a chance to ask lib/LTO to keep it. This patch fixes it by having a more direct implementation of the gold API. If it asks us to keep a symbol, we change the linkage so it is not linkonce. If it says we can drop a symbol, we do so. All of this before we even send the module to lib/Linker. Since now we don't have to produce LTO_SYMBOL_SCOPE_DEFAULT_CAN_BE_HIDDEN, during symbol resolution we can use a temporary LLVMContext and do lazy module loading. This allows us to keep the minimum possible amount of allocated memory around. This should also allow as much parallelism as we want, since there is no shared context. llvm-svn: 216215 2014-08-21 22:28:55 +02:00			`; RUN: llvm-as %s -o %t.o`
			`; RUN: llvm-as %p/Inputs/alias-1.ll -o %t2.o`
			`; RUN: ld -shared -o %t3.o -plugin %llvmshlibdir/LLVMgold.so %t2.o %t.o \`
			`; RUN: -plugin-opt=emit-llvm`
			`; RUN: llvm-dis %t3.o -o - \| FileCheck %s`

			`; CHECK: @a = global i32 42`
			`; CHECK: @b = global i32 1`

			`@a = weak alias i32* @b`
			`@b = global i32 1`