llvm-mirror/test/Linker/ctors2.ll

; RUN: llvm-link -S %s %p/Inputs/ctors2.ll -o - | FileCheck %s

$foo = comdat any
@foo = global i8 0, comdat

; CHECK: @llvm.global_ctors = appending global [0 x { i32, void ()*, i8* }] zeroinitializer
; CHECK: @foo = global i8 0, comdat
Correctly handle llvm.global_ctors merging. We were not handling the case where an entry must be dropped and the destination module has no llvm.global_ctors. llvm-svn: 254241 2015-11-29 04:29:42 +01:00			`; RUN: llvm-link -S %s %p/Inputs/ctors2.ll -o - \| FileCheck %s`

			`$foo = comdat any`
			`@foo = global i8 0, comdat`

			`; CHECK: @llvm.global_ctors = appending global [0 x { i32, void (), i8 }] zeroinitializer`
Preserve the lexical order for global variables during llvm-link merge The order of global variables is generated in the order of recursively materializing variables if the global variable has the attribute of hasLocalLinkage or hasLinkOnceLinkage during the module merging. In practice, it is often the exact reverse of source order. This new order may cause performance regression. The change is to preserve the original lexical order for global variables. Reviewed By: jdoerfert, dexonsmith Differential Revision: https://reviews.llvm.org/D94202 2021-04-24 07:37:08 +02:00			`; CHECK: @foo = global i8 0, comdat`