File: dont-introduce-addrspacecast.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 1,998,492 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (42 lines) | stat: -rw-r--r-- 1,079 bytes parent folder | download | duplicates (8) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
 
; RUN: opt -S -passes='require<profile-summary>,function(codegenprepare)' < %s | FileCheck %s

target datalayout = "e-i64:64-v16:16-v32:32-n16:32:64"
target triple = "nvptx64-nvidia-cuda"


; ptrtoint/inttoptr combinations can introduce semantically-meaningful address space casts
; which we can't sink into an addrspacecast

; CHECK-LABEL: @test
define void @test(ptr %input_ptr) {
  ; CHECK-LABEL: l1:
  ; CHECK-NOT: addrspacecast
  %intptr = ptrtoint ptr %input_ptr to i64
  %ptr = inttoptr i64 %intptr to ptr addrspace(3)

  br label %l1
l1:

  store atomic i32 1, ptr addrspace(3) %ptr unordered, align 4
  ret void
}


; we still should be able to look through multiple sequences of inttoptr/ptrtoint

; CHECK-LABEL: @test2
define void @test2(ptr %input_ptr) {
  ; CHECK-LABEL: l2:
  ; CHECK-NEXT: store
  %intptr = ptrtoint ptr %input_ptr to i64
  %ptr = inttoptr i64 %intptr to ptr addrspace(3)

  %intptr2 = ptrtoint ptr addrspace(3) %ptr to i64
  %ptr2 = inttoptr i64 %intptr2 to ptr

  br label %l2
l2:

  store atomic i32 1, ptr %ptr2 unordered, align 4
  ret void
}