mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 04:02:41 +01:00
86643b627c
If the landingpad of the invoke is using a personality function that catches asynch exceptions, then it can catch a trap. Also add some landingpads to invalid LLVM IR test cases that lack them. Over-the-shoulder reviewed by David Majnemer. llvm-svn: 228782
32 lines
814 B
LLVM
32 lines
814 B
LLVM
; RUN: opt -S -simplifycfg < %s | FileCheck %s
|
|
|
|
; Don't remove invokes of nounwind functions if the personality handles async
|
|
; exceptions. The @div function in this test can fault, even though it can't
|
|
; throw a synchronous exception.
|
|
|
|
define i32 @div(i32 %n, i32 %d) nounwind {
|
|
entry:
|
|
%div = sdiv i32 %n, %d
|
|
ret i32 %div
|
|
}
|
|
|
|
define i32 @main() nounwind {
|
|
entry:
|
|
%call = invoke i32 @div(i32 10, i32 0)
|
|
to label %__try.cont unwind label %lpad
|
|
|
|
lpad:
|
|
%0 = landingpad { i8*, i32 } personality i8* bitcast (i32 (...)* @__C_specific_handler to i8*)
|
|
catch i8* null
|
|
br label %__try.cont
|
|
|
|
__try.cont:
|
|
%retval.0 = phi i32 [ %call, %entry ], [ 0, %lpad ]
|
|
ret i32 %retval.0
|
|
}
|
|
|
|
; CHECK-LABEL: define i32 @main()
|
|
; CHECK: invoke i32 @div(i32 10, i32 0)
|
|
|
|
declare i32 @__C_specific_handler(...)
|