llvm-capstone/llvm/test/Linker/2003-01-30-LinkerRename.ll

; 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
}
Make this test a bit stricter. This now: * Forces the linker to include the internal definition. * Checks the full output. llvm-svn: 220494 2014-10-23 18:44:07 +00:00			`; RUN: llvm-as %S/Inputs/2003-01-30-LinkerRename.ll -o %t.1.bc`
Remove obsolete -f flags. llvm-svn: 79992 2009-08-25 15:38:29 +00:00			`; RUN: llvm-as %s -o %t.2.bc`
Rewrite test/Linker tests to use FileCheck instead of grep. Some translations here are not 1x1 because there are grep\|grep chains that are non-trivial to implement in terms of FileCheck features. I made an effort for the tests to remain as similar as possible; do let me know if you notice anything fishy. The good news are that some buggy tests were fixed (grep \| not grep - a bug waiting to happen). llvm-svn: 179102 2013-04-09 16:51:13 +00:00			`; RUN: llvm-link %t.1.bc %t.2.bc -S \| FileCheck %s`
NEw testcase llvm-svn: 5438 2003-01-30 19:28:01 +00:00
Have a single way for creating unique value names. 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 2015-11-22 00:16:24 +00:00			`; CHECK: @bar = global i32 ()* @foo.2`
Make this test a bit stricter. This now: * Forces the linker to include the internal definition. * Checks the full output. llvm-svn: 220494 2014-10-23 18:44:07 +00:00
Have a single way for creating unique value names. 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 2015-11-22 00:16:24 +00:00			`; CHECK: define internal i32 @foo.2() {`
Make this test a bit stricter. This now: * Forces the linker to include the internal definition. * Checks the full output. llvm-svn: 220494 2014-10-23 18:44:07 +00:00			`; CHECK-NEXT: ret i32 7`
			`; CHECK-NEXT: }`

			`; CHECK: define i32 @foo() {`
			`; CHECK-NEXT: ret i32 0`
			`; CHECK-NEXT: }`
NEw testcase llvm-svn: 5438 2003-01-30 19:28:01 +00:00
Make this test a bit stricter. This now: * Forces the linker to include the internal definition. * Checks the full output. llvm-svn: 220494 2014-10-23 18:44:07 +00:00			`define i32 @foo() {`
			`ret i32 0`
			`}`