It's currently not safe to outline landingpad instructions (see
llvm.org/PR39917). Like @llvm.eh.typeid.for, the order and content of
previous landingpad instructions in a function alters the lowering of
subsequent landingpads by renumbering type info ID's. Outlining a
landingpad therefore breaks exception handling & unwinding.
llvm-svn: 348870
/// Check whether it's safe to outline \p BB.
static bool mayExtractBlock(const BasicBlock &BB) {
- return !BB.hasAddressTaken();
+ return !BB.hasAddressTaken() && !BB.isEHPad();
}
/// Check whether \p Region is profitable to outline.
ret void
}
+; See llvm.org/PR39917. It's currently not safe to outline landingpad
+; instructions.
+;
; CHECK-LABEL: define {{.*}}@bar(
-; CHECK-NOT: landingpad
+; CHECK: landingpad
define void @bar(i32 %cond) personality i8 0 {
entry:
br i1 undef, label %exit, label %continue
; CHECK: sideeffect(i32 1)
; CHECK: sink
-; CHECK-LABEL: define {{.*}}@bar.cold.1(
-; CHECK: sideeffect(i32 0)
-; CHECK: sideeffect(i32 1)
-
declare void @sideeffect(i32)
declare void @sink() cold