File: unreachable-regression.ll

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-12
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,496,180 kB
  • sloc: cpp: 5,593,972; ansic: 986,872; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,538; xml: 953; cs: 573; fortran: 567
file content (34 lines) | stat: -rw-r--r-- 1,127 bytes parent folder | download | duplicates (14)
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
; RUN: opt -S -rewrite-statepoints-for-gc < %s | FileCheck %s
; RUN: opt -S -passes=rewrite-statepoints-for-gc < %s | FileCheck %s
;
; Regression test:
;   After the rewritable callsite collection if any callsite was found
;   in a block that was reported unreachable by DominanceTree then
;   removeUnreachableBlocks() was called. But it is stronger than
;   DominatorTree::isReachableFromEntry(), i.e. removeUnreachableBlocks
;   can remove some blocks for which isReachableFromEntry() returns true.
;   This resulted in stale pointers to the collected but removed
;   callsites. Such stale pointers caused crash when accessed.
declare void @f(i8 addrspace(1)* %obj)

define void @test(i8 addrspace(1)* %arg) gc "statepoint-example" {
; CHECK-LABEL: test(
; CHECK-NEXT: @f
 call void @f(i8 addrspace(1)* %arg) #1
 br i1 true, label %not_zero, label %zero

not_zero:
 ret void

; This block is reachable but removed by removeUnreachableBlocks()
zero:
; CHECK-NOT: @f
 call void @f(i8 addrspace(1)* %arg) #1
 ret void

unreach:
 call void @f(i8 addrspace(1)* %arg) #1
 ret void
}

attributes #1 = { norecurse noimplicitfloat }