mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-11-23 22:00:10 +00:00
d1beb07d39
We had two code paths. One would create names like "foo.1" and the other names like "foo1". For globals it is important to use "foo.1" to help C++ name demangling. For locals there is no strong reason to go one way or the other so I kept the most common mangling (foo1). llvm-svn: 253804
18 lines
382 B
LLVM
18 lines
382 B
LLVM
; RUN: llvm-as %S/Inputs/2003-01-30-LinkerRename.ll -o %t.1.bc
|
|
; RUN: llvm-as %s -o %t.2.bc
|
|
; RUN: llvm-link %t.1.bc %t.2.bc -S | FileCheck %s
|
|
|
|
; CHECK: @bar = global i32 ()* @foo.2
|
|
|
|
; CHECK: define internal i32 @foo.2() {
|
|
; CHECK-NEXT: ret i32 7
|
|
; CHECK-NEXT: }
|
|
|
|
; CHECK: define i32 @foo() {
|
|
; CHECK-NEXT: ret i32 0
|
|
; CHECK-NEXT: }
|
|
|
|
define i32 @foo() {
|
|
ret i32 0
|
|
}
|