maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Transforms/GlobalOpt/2009-03-06-Anonymous.ll

24 lines
341 B
LLVM
Raw Normal View History

GlobalOpt: FileCheck-ize test No functionality change. llvm-svn: 212103
2014-07-01 23:26:47 +08:00
; RUN: opt < %s -globalopt -S | FileCheck %s
While thinking about the one-definition-rule and trying to find a tiny mouse hole to squeeze through, it struck me that globals without a name can be considered internal since they can't be referenced from outside the current module. This patch makes GlobalOpt give them internal linkage. Also done for aliases even though they always have names, since in my opinion anonymous aliases should be allowed for consistency with global variables and functions. So if that happens one day, this code is ready! llvm-svn: 66267
2009-03-06 18:21:56 +08:00
global i32 0
GlobalOpt: Don't swap private for internal linkage There were transforms whose *intent* was to downgrade the linkage of external objects to have internal linkage. However, it fired on things with private linkage as well. llvm-svn: 212104
2014-07-01 23:26:50 +08:00
; CHECK-DAG: @0 = internal global i32 0
private global i32 0
; CHECK-DAG: @1 = private global i32 0
define i32* @2() {
While thinking about the one-definition-rule and trying to find a tiny mouse hole to squeeze through, it struck me that globals without a name can be considered internal since they can't be referenced from outside the current module. This patch makes GlobalOpt give them internal linkage. Also done for aliases even though they always have names, since in my opinion anonymous aliases should be allowed for consistency with global variables and functions. So if that happens one day, this code is ready! llvm-svn: 66267
2009-03-06 18:21:56 +08:00
ret i32* @0
}
GlobalOpt: Don't swap private for internal linkage There were transforms whose *intent* was to downgrade the linkage of external objects to have internal linkage. However, it fired on things with private linkage as well. llvm-svn: 212104
2014-07-01 23:26:50 +08:00
; CHECK-DAG: define internal fastcc i32* @2()
While thinking about the one-definition-rule and trying to find a tiny mouse hole to squeeze through, it struck me that globals without a name can be considered internal since they can't be referenced from outside the current module. This patch makes GlobalOpt give them internal linkage. Also done for aliases even though they always have names, since in my opinion anonymous aliases should be allowed for consistency with global variables and functions. So if that happens one day, this code is ready! llvm-svn: 66267
2009-03-06 18:21:56 +08:00
define i32* @f() {
entry:
GlobalOpt: Don't swap private for internal linkage There were transforms whose *intent* was to downgrade the linkage of external objects to have internal linkage. However, it fired on things with private linkage as well. llvm-svn: 212104
2014-07-01 23:26:50 +08:00
call i32* @2()
While thinking about the one-definition-rule and trying to find a tiny mouse hole to squeeze through, it struck me that globals without a name can be considered internal since they can't be referenced from outside the current module. This patch makes GlobalOpt give them internal linkage. Also done for aliases even though they always have names, since in my opinion anonymous aliases should be allowed for consistency with global variables and functions. So if that happens one day, this code is ready! llvm-svn: 66267
2009-03-06 18:21:56 +08:00
ret i32* %0
}
GlobalOpt: Don't swap private for internal linkage There were transforms whose *intent* was to downgrade the linkage of external objects to have internal linkage. However, it fired on things with private linkage as well. llvm-svn: 212104
2014-07-01 23:26:50 +08:00
define i32* @g() {
entry:
ret i32* @1
}