aboutsummaryrefslogtreecommitdiffstats
path: root/test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll
diff options
context:
space:
mode:
Diffstat (limited to 'test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll')
-rw-r--r--test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll24
1 files changed, 24 insertions, 0 deletions
diff --git a/test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll b/test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll
new file mode 100644
index 0000000..c33f9e9
--- /dev/null
+++ b/test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.ll
@@ -0,0 +1,24 @@
+; Test for a problem afflicting several C++ programs in the testsuite. The
+; instcombine pass is trying to get rid of the cast in the invoke instruction,
+; inserting a cast of the return value after the PHI instruction, but which is
+; used by the PHI instruction. This is bad: because of the semantics of the
+; invoke instruction, we really cannot perform this transformation at all at
+; least without splitting the critical edge.
+;
+; RUN: llvm-as < %s | opt -instcombine -disable-output
+
+declare sbyte* %test()
+
+int %foo() {
+entry:
+ br bool true, label %cont, label %call
+call:
+ %P = invoke int*()* cast (sbyte*()* %test to int*()*)()
+ to label %cont except label %N
+cont:
+ %P2 = phi int* [%P, %call], [null, %entry]
+ %V = load int* %P2
+ ret int %V
+N:
+ ret int 0
+}