llvm-project/llvm/test/CodeGen/ARM/2012-09-25-InlineAsmScalarT...

; RUN: not llc -mtriple=arm-eabi -mcpu=cortex-a8 %s -o - 2>&1 | FileCheck %s

; Check for error message:
; CHECK: non-trivial scalar-to-vector conversion, possible invalid constraint for vector type

define void @f() nounwind ssp {
  %1 = call { <2 x i64>, <2 x i64>, <2 x i64>, <2 x i64> } asm "vldm $4, { ${0:q}, ${1:q}, ${2:q}, ${3:q} }", "=r,=r,=r,=r,r"(i64* undef) nounwind, !srcloc !0
  ret void
}

!0 = metadata !{i32 318437}
ARM: fixup more tests to specify the target more explicitly This changes the tests that were targeting ARM EABI to explicitly specify the environment rather than relying on the default. This breaks with the new Windows on ARM support when running the tests on Windows where the default environment is no longer EABI. Take the opportunity to avoid a pointless redirect (helps when trying to debug with providing a command line invocation which can be copy and pasted) and removing a few greps in favour of FileCheck. llvm-svn: 205541 2014-04-04 00:01:44 +08:00			`; RUN: not llc -mtriple=arm-eabi -mcpu=cortex-a8 %s -o - 2>&1 \| FileCheck %s`
Generate an error message instead of asserting or segfaulting when we have a scalar-to-vector conversion that we cannot handle. For instance, when an invalid constraint is used in an inline asm statement. <rdar://problem/12284092> llvm-svn: 164657 2012-09-26 12:04:19 +08:00
			`; Check for error message:`
			`; CHECK: non-trivial scalar-to-vector conversion, possible invalid constraint for vector type`

			`define void @f() nounwind ssp {`
			`%1 = call { <2 x i64>, <2 x i64>, <2 x i64>, <2 x i64> } asm "vldm $4, { ${0:q}, ${1:q}, ${2:q}, ${3:q} }", "=r,=r,=r,=r,r"(i64* undef) nounwind, !srcloc !0`
			`ret void`
			`}`

			`!0 = metadata !{i32 318437}`