llvm-mirror/test/Linker/broken.ll

; RUN: not llvm-link -o /dev/null %s 2>&1 | FileCheck %s

; CHECK: broken.ll: error: input module is broken!
define i32 @foo(i32 %v) {
  %first = add i32 %v, %second
  %second = add i32 %v, 3
  ret i32 %first
}
llvm-link: Verify input modules Otherwise, broken input modules can cause assertions. I've updated two of the testcases that started failing (modules that had `Require` flags but didn't meet their own requirements), but Rafael and I decided that test/Linker/2011-08-22-ResolveAlias.ll should just be deleted outright -- it's a leftover of the way llvm-gcc used to implement weakref. llvm-svn: 233229 2015-03-25 23:22:10 +00:00			`; RUN: not llvm-link -o /dev/null %s 2>&1 \| FileCheck %s`

tools: Unify how verifyModule() is called Unify the error messages for the various tools when `verifyModule()` fails on an input module. The "brave new way" is: lltool: path/to/input.ll: error: input module is broken! llvm-svn: 233667 2015-03-31 03:07:23 +00:00			`; CHECK: broken.ll: error: input module is broken!`
llvm-link: Verify input modules Otherwise, broken input modules can cause assertions. I've updated two of the testcases that started failing (modules that had `Require` flags but didn't meet their own requirements), but Rafael and I decided that test/Linker/2011-08-22-ResolveAlias.ll should just be deleted outright -- it's a leftover of the way llvm-gcc used to implement weakref. llvm-svn: 233229 2015-03-25 23:22:10 +00:00			`define i32 @foo(i32 %v) {`
			`%first = add i32 %v, %second`
			`%second = add i32 %v, 3`
			`ret i32 %first`
			`}`