New testcase that SCCP miscompiles. Luckily this is extremely unlikely to
authorChris Lattner <sabre@nondot.org>
Fri, 10 Dec 2004 20:10:23 +0000 (20:10 +0000)
committerChris Lattner <sabre@nondot.org>
Fri, 10 Dec 2004 20:10:23 +0000 (20:10 +0000)
happen in practice, but IP-SCCP can trigger it.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@18773 91177308-0d34-0410-b5e6-96231b3b80d8

test/Transforms/SCCP/2004-12-10-UndefBranchBug.ll [new file with mode: 0644]

diff --git a/test/Transforms/SCCP/2004-12-10-UndefBranchBug.ll b/test/Transforms/SCCP/2004-12-10-UndefBranchBug.ll
new file mode 100644 (file)
index 0000000..be6944c
--- /dev/null
@@ -0,0 +1,11 @@
+; RUN: llvm-as < %s | opt -sccp | llvm-dis | grep 'ret int 1'
+
+; This function definitely returns 1, even if we don't know the direction
+; of the branch.
+
+int %foo() {
+       br bool undef, label %T, label %T
+T:
+       %X = add int 0, 1
+       ret int %X
+}