mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-22 18:54:02 +01:00
ae19e5c0f7
Most users won't have to worry about this as all of the 'getOrInsertFunction' functions on Module will default to the program address space. An overload has been added to Function::Create to abstract away the details for most callers. This is based on https://reviews.llvm.org/D37054 but without the changes to make passing a Module to Function::Create() mandatory. I have also added some more tests and fixed the LLParser to accept call instructions for types in the program address space. Reviewed By: bjope Differential Revision: https://reviews.llvm.org/D47541 llvm-svn: 340519
23 lines
1.0 KiB
LLVM
23 lines
1.0 KiB
LLVM
; RUN: not llvm-as %s -o /dev/null 2>&1 | FileCheck %s
|
|
; RUN: llvm-as %s -data-layout=P42 -o - | llvm-dis - -o - | FileCheck %s -check-prefix PROGAS42
|
|
|
|
; Check that numbered variables in a nonzero program address space 200 can be used in a call instruction
|
|
|
|
define i8 @test_unnamed(i8(i32)*, i8(i32) addrspace(42)*) {
|
|
; Calls with explicit address spaces are fine:
|
|
call addrspace(0) i8 %0(i32 0)
|
|
call addrspace(42) i8 %1(i32 0)
|
|
; this call is fine if the program address space is 42
|
|
call i8 %1(i32 0)
|
|
; CHECK: call-nonzero-program-addrspace-2.ll:[[@LINE-1]]:11: error: '%1' defined with type 'i8 (i32) addrspace(42)*' but expected 'i8 (i32)*'
|
|
ret i8 0
|
|
}
|
|
|
|
; PROGAS42: target datalayout = "P42"
|
|
; PROGAS42: define i8 @test_unnamed(i8 (i32)*, i8 (i32) addrspace(42)*) addrspace(42) {
|
|
; PROGAS42-NEXT: %3 = call addrspace(0) i8 %0(i32 0)
|
|
; PROGAS42-NEXT: %4 = call addrspace(42) i8 %1(i32 0)
|
|
; PROGAS42-NEXT: %5 = call addrspace(42) i8 %1(i32 0)
|
|
; PROGAS42-NEXT: ret i8 0
|
|
; PROGAS42-NEXT: }
|