llvm-mirror/test/Assembler/alloca-addrspace-parse-error-1.ll

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

target datalayout = "A1"

; addrspace and align in wrong order
; CHECK: :8:39: error: expected metadata after comma
define void @use_alloca() {
  %alloca = alloca i32, addrspace(1), align 4
  ret void
}

!0 = !{}
Allow DataLayout to specify addrspace for allocas. LLVM makes several assumptions about address space 0. However, alloca is presently constrained to always return this address space. There's no real way to avoid using alloca, so without this there is no way to opt out of these assumptions. The problematic assumptions include: - That the pointer size used for the stack is the same size as the code size pointer, which is also the maximum sized pointer. - That 0 is an invalid, non-dereferencable pointer value. These are problems for AMDGPU because alloca is used to implement the private address space, which uses a 32-bit index as the pointer value. Other pointers are 64-bit and behave more like LLVM's notion of generic address space. By changing the address space used for allocas, we can change our generic pointer type to be LLVM's generic pointer type which does have similar properties. llvm-svn: 299888 2017-04-11 00:27:50 +02:00			`; RUN: not llvm-as < %s 2>&1 \| FileCheck %s`

			`target datalayout = "A1"`

			`; addrspace and align in wrong order`
			`; CHECK: :8:39: error: expected metadata after comma`
			`define void @use_alloca() {`
			`%alloca = alloca i32, addrspace(1), align 4`
			`ret void`
			`}`

			`!0 = !{}`