File: outgoing_edge.ll

package info (click to toggle)
llvm-toolchain-20 1%3A20.1.6-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 2,111,304 kB
  • sloc: cpp: 7,438,677; ansic: 1,393,822; asm: 1,012,926; python: 241,650; f90: 86,635; objc: 75,479; lisp: 42,144; pascal: 17,286; sh: 10,027; ml: 5,082; perl: 4,730; awk: 3,523; makefile: 3,349; javascript: 2,251; xml: 892; fortran: 672
file content (32 lines) | stat: -rw-r--r-- 1,083 bytes parent folder | download | duplicates (18) 
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
 
; REQUIRES: asserts
; RUN: opt < %s -passes='print<regions>' 2>&1 | FileCheck %s

; While working on improvements to the region info analysis, this test
; case caused an incorrect region bb2 => bb3 to be detected. It is incorrect
; because bb2 has an outgoing edge to bb4. This is interesting because
; bb2 dom bb3 and bb3 pdom bb2, which should have been enough to prevent incoming
; forward edges into the region and outgoing forward edges from the region.

define void @meread_() nounwind {
bb:
   br label %bb1

bb1:                                              ; preds = %bb4, %bb
   br label %bb2

bb2:                                              ; preds = %bb1
  br i1 true, label %bb3, label %bb4

bb3:                                              ; preds = %bb2
  br i1 true, label %bb4, label %bb5

bb4:                                              ; preds = %bb3, %bb2
   br label %bb1

bb5:                                              ; preds = %bb3
   ret void
 }

; CHECK:      [0] bb => <Function Return>
; CHECK-NEXT:   [1] bb1 => bb5
; CHECK-NEXT: End region tree