File: thread-two-bbs-msvc.ll

package info (click to toggle)
llvm-toolchain-16 1%3A16.0.6-15~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,634,792 kB
  • sloc: cpp: 6,179,261; ansic: 1,216,205; asm: 741,319; python: 196,614; objc: 75,325; f90: 49,640; lisp: 32,396; pascal: 12,286; sh: 9,394; perl: 7,442; ml: 5,494; awk: 3,523; makefile: 2,723; javascript: 1,206; xml: 886; fortran: 581; cs: 573
file content (39 lines) | stat: -rw-r--r-- 1,123 bytes parent folder | download | duplicates (12)
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
; RUN: opt -S -passes=jump-threading,verify < %s | FileCheck %s

target datalayout = "e-m:w-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-pc-windows-msvc19.16.27026"

; Verify that we do *not* thread any edge.  On Windows, we used to
; improperly duplicate EH pads like bb_cleanup below, resulting in an
; assertion failure later down the pass pipeline.
define void @foo(ptr %0) personality ptr @baz {
; CHECK-LABEL: @foo
; CHECK-NOT: bb_{{[^ ]*}}.thread:
entry:
  invoke void @bar()
          to label %bb_invoke unwind label %bb_cleanuppad

bb_invoke:
  invoke void @bar()
          to label %bb_exit unwind label %bb_cleanuppad

bb_cleanuppad:
  %index = phi i64 [ 1, %bb_invoke ], [ 0, %entry ]
  %cond1 = phi i1 [ false, %bb_invoke ], [ true, %entry ]
  %1 = cleanuppad within none []
  br i1 %cond1, label %bb_action, label %bb_cleanupret

bb_action:
  %cond2 = icmp eq i64 %index, 0
  br i1 %cond2, label %bb_cleanupret, label %bb_exit

bb_exit:
  call void @bar()
  ret void

bb_cleanupret:
  cleanupret from %1 unwind to caller
}

declare void @bar()
declare i32 @baz()