File: call-nonzero-program-addrspace-2.ll

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-6~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 1,418,812 kB
  • sloc: cpp: 5,290,827; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,900; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,892; xml: 953; cs: 573; fortran: 539
file content (22 lines) | stat: -rw-r--r-- 1,035 bytes parent folder | download | duplicates (9) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
; 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)* %0) {
  ; 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)* %0, i8 (i32) addrspace(42)* %1) 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:  }