mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-19 11:02:59 +02:00
673715d427
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
28 lines
693 B
LLVM
28 lines
693 B
LLVM
; Test the order of global variables during llvm-link
|
|
|
|
; RUN: llvm-link %s %S/Inputs/globalorder-2.ll -o %t.bc
|
|
; RUN: llvm-dis -o - %t.bc | FileCheck %s
|
|
|
|
@var1 = internal global i32 0, align 4
|
|
@var2 = internal global i32 0, align 4
|
|
@var3 = global i32* @var1, align 4
|
|
@var4 = global i32* @var2, align 4
|
|
|
|
define i32 @foo() {
|
|
entry:
|
|
%0 = load i32*, i32** @var3, align 4
|
|
%1 = load i32, i32* %0, align 4
|
|
%2 = load i32*, i32** @var4, align 4
|
|
%3 = load i32, i32* %2, align 4
|
|
%add = add nsw i32 %3, %1
|
|
ret i32 %add
|
|
}
|
|
; CHECK: @var1 =
|
|
; CHECK-NEXT: @var2 =
|
|
; CHECK-NEXT: @var3 =
|
|
; CHECK-NEXT: @var4 =
|
|
; CHECK-NEXT: @var5 =
|
|
; CHECK-NEXT: @var6 =
|
|
; CHECK-NEXT: @var7 =
|
|
; CHECK-NEXT: @var8 =
|