1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-24 11:42:57 +01:00
llvm-mirror/test/Transforms/LoopUnroll/unroll-cleanuppad.ll
David Majnemer b545ac7cd4 [LoopUnroll] Unroll loops which have exit blocks to EH pads
We were overly cautious in our analysis of loops which have invokes
which unwind to EH pads.  The loop unroll transform is safe because it
only clones blocks in the loop body, it does not try to split critical
edges involving EH pads.  Instead, move the necessary safety check to
LoopUnswitch.

N.B. The safety check for loop unswitch is covered by an existing test
which fails without it.

llvm-svn: 268357
2016-05-03 03:57:40 +00:00

41 lines
1.1 KiB
LLVM

; RUN: opt -S -loop-unroll %s | FileCheck %s
target datalayout = "e-m:w-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-pc-windows-msvc18.0.0"
define void @test1() personality i32 (...)* @__CxxFrameHandler3 {
entry:
br label %for.body
for.body: ; preds = %entry, %for.inc
%phi = phi i32 [ 0, %entry ], [ %inc, %for.inc ]
invoke void @callee(i32 %phi)
to label %for.inc unwind label %ehcleanup
for.inc: ; preds = %for.body
%inc = add nuw nsw i32 %phi, 1
%cmp = icmp slt i32 %inc, 3
br i1 %cmp, label %for.body, label %for.cond.cleanup
for.cond.cleanup: ; preds = %for.inc
call void @dtor()
ret void
ehcleanup: ; preds = %for.body
%cp = cleanuppad within none []
call void @dtor() [ "funclet"(token %cp) ]
cleanupret from %cp unwind to caller
}
; CHECK-LABEL: define void @test1(
; CHECK: invoke void @callee(i32 0
; CHECK: invoke void @callee(i32 1
; CHECK: invoke void @callee(i32 2
declare void @callee(i32)
declare i32 @__CxxFrameHandler3(...)
declare void @dtor()