llvm-mirror/test/Assembler/invalid_cast2.ll

; RUN: not llvm-as < %s 2>&1 | FileCheck %s

; CHECK: invalid cast opcode for cast from '<4 x i64>' to 'i8'

define i8 @foo(<4 x i64> %x) {
  %y = trunc <4 x i64> %x to i8
  ret i8 %y
}
Convert the uses of '\|&' to use '2>&1 \|' instead, which works on old versions of Bash. In addition, I can back out the change to the lit built-in shell test runner to support this. This should fix the majority of fallout on Darwin, but I suspect there will be a few straggling issues. llvm-svn: 159544 2012-07-02 20:37:59 +02:00			`; RUN: not llvm-as < %s 2>&1 \| FileCheck %s`
FileCheckize these testcases. llvm-svn: 154281 2012-04-08 13:00:38 +02:00
			`; CHECK: invalid cast opcode for cast from '<4 x i64>' to 'i8'`
Tighten up checking of the validity of casts. (1) The IR parser would happily accept things like "sext <2 x i32> to <999 x i64>". It would also accept "sext <2 x i32> to i64", though the verifier would catch that later. Fixed by having castIsValid check that vector lengths match except when doing a bitcast. (2) When creating a cast instruction, check that the cast is valid (this was already done when creating constexpr casts). While there, replace getScalarSizeInBits (used to allow more vector casts) with getPrimitiveSizeInBits in getCastOpcode and isCastable since vector to vector casts are now handled explicitly by passing to the element types; i.e. this bit should result in no functional change. llvm-svn: 131532 2011-05-18 11:21:57 +02:00
			`define i8 @foo(<4 x i64> %x) {`
			`%y = trunc <4 x i64> %x to i8`
			`ret i8 %y`
			`}`