maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Bitcode/local-linkage-default-visib...

81 lines
2.3 KiB
LLVM
Raw Normal View History

IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
; RUN: llvm-dis < %s.bc | FileCheck %s
verify-uselistorder: Force -preserve-bc-use-list-order llvm-svn: 216022
2014-08-20 05:08:27 +08:00
; RUN: verify-uselistorder < %s.bc
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
; local-linkage-default-visibility.3.4.ll.bc was generated by passing this file
; to llvm-as-3.4. The test checks that LLVM upgrades visibility of symbols
; with local linkage to default visibility.
@default.internal.var = internal global i32 0
; CHECK: @default.internal.var = internal global i32 0
@hidden.internal.var = internal hidden global i32 0
; CHECK: @hidden.internal.var = internal global i32 0
@protected.internal.var = internal protected global i32 0
; CHECK: @protected.internal.var = internal global i32 0
@default.private.var = private global i32 0
; CHECK: @default.private.var = private global i32 0
@hidden.private.var = private hidden global i32 0
; CHECK: @hidden.private.var = private global i32 0
@protected.private.var = private protected global i32 0
; CHECK: @protected.private.var = private global i32 0
@global = global i32 0
@default.internal.alias = alias internal i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @default.internal.alias = internal alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
@hidden.internal.alias = hidden alias internal i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @hidden.internal.alias = internal alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
@protected.internal.alias = protected alias internal i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @protected.internal.alias = internal alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
@default.private.alias = alias private i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @default.private.alias = private alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
@hidden.private.alias = hidden alias private i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @hidden.private.alias = private alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
@protected.private.alias = protected alias private i32* @global
Use "weak alias" instead of "alias weak" Before this patch we had @a = weak global ... but @b = alias weak ... The patch changes aliases to look more like global variables. Looking at some really old code suggests that the reason was that the old bison based parser had a reduction for alias linkages and another one for global variable linkages. Putting the alias first avoided the reduce/reduce conflict. The days of the old .ll parser are long gone. The new one parses just "linkage" and a later check is responsible for deciding if a linkage is valid in a given context. llvm-svn: 214355
2014-07-31 06:51:54 +08:00
; CHECK: @protected.private.alias = private alias i32* @global
IR: Don't allow non-default visibility on local linkage Visibilities of `hidden` and `protected` are meaningless for symbols with local linkage. - Change the assembler to reject non-default visibility on symbols with local linkage. - Change the bitcode reader to auto-upgrade `hidden` and `protected` to `default` when the linkage is local. - Update LangRef. <rdar://problem/16141113> llvm-svn: 208263
2014-05-08 06:57:20 +08:00
define internal void @default.internal() {
; CHECK: define internal void @default.internal
entry:
ret void
}
define internal hidden void @hidden.internal() {
; CHECK: define internal void @hidden.internal
entry:
ret void
}
define internal protected void @protected.internal() {
; CHECK: define internal void @protected.internal
entry:
ret void
}
define private void @default.private() {
; CHECK: define private void @default.private
entry:
ret void
}
define private hidden void @hidden.private() {
; CHECK: define private void @hidden.private
entry:
ret void
}
define private protected void @protected.private() {
; CHECK: define private void @protected.private
entry:
ret void
}