1; RUN: llc -verify-machineinstrs < %s | FileCheck %s
2
3; We used to have an issue where we inserted an MBB between invoke.cont.3 and
4; its fallthrough target of ret void.
5
6target datalayout = "e-m:x-p:32:32-i64:64-f80:32-n8:16:32-a:0:32-S32"
7target triple = "i386-pc-windows-msvc18.0.0"
8
9@some_global = global i32 0
10
11declare i32 @__CxxFrameHandler3(...)
12
13declare void @g()
14
15define void @f() personality i32 (...)* @__CxxFrameHandler3 {
16entry:
17  invoke void @g()
18          to label %invoke.cont.3 unwind label %catch.dispatch
19
20catch.dispatch:                                   ; preds = %entry
21  %0 = catchpad [i8* null, i32 64, i8* null]
22          to label %catch unwind label %catchendblock
23
24catch:                                            ; preds = %catch.dispatch
25  catchret %0 to label %nrvo.skipdtor
26
27catchendblock:                                    ; preds = %catch, %catch.dispatch
28  catchendpad unwind to caller
29
30invoke.cont.3:                                    ; preds = %entry
31  store i32 123, i32* @some_global
32  br label %nrvo.skipdtor
33
34nrvo.skipdtor:                                    ; preds = %invoke.cont.3, %invoke.cont.4
35  ret void
36}
37
38; CHECK-LABEL: _f: # @f
39; CHECK: calll _g
40; CHECK: movl $123, _some_global
41; CHECK-NOT: jmp
42; CHECK-NOT: movl {{.*}}, %esp
43; CHECK: retl
44; CHECK: addl $12, %ebp
45; CHECK: jmp LBB0_{{.*}}
46