llvm-6502/test/Assembler/invalid_cast.ll

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

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

define <3 x i8> @foo(<4 x i64> %x) {
  %y = trunc <4 x i64> %x to <3 x i8>
  ret <3 x i8> %y
}
FileCheckize these testcases. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154281 91177308-0d34-0410-b5e6-96231b3b80d8 2012-04-08 11:00:38 +00:00			`; RUN: not llvm-as < %s \|& FileCheck %s`

			`; CHECK: invalid cast opcode for cast from '<4 x i64>' to '<3 x 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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@131532 91177308-0d34-0410-b5e6-96231b3b80d8 2011-05-18 09:21:57 +00:00
			`define <3 x i8> @foo(<4 x i64> %x) {`
			`%y = trunc <4 x i64> %x to <3 x i8>`
			`ret <3 x i8> %y`
			`}`