Add a few test cases to ensure the bitcode reader is backward compatible with

LLVM 2.9.  My understanding is that we plan to maintain compatibility with 2.9
until the 3.1 release.  At that time we can generate new test cases using LLVM
3.0.

llvm-svn: 142958

4 files changed, 10 insertions, 0 deletions

diff --git a/llvm/test/Bitcode/fbench-llvm-2.9.ll b/llvm/test/Bitcode/fbench-llvm-2.9.ll
new file mode 100644
index 00000000000..588769159f2
--- /dev/null
+++ b/llvm/test/Bitcode/fbench-llvm-2.9.ll
@@ -0,0 +1,5 @@
+; This isn't really an assembly file. It just runs the test on the bitcode to 
+; ensure bitcode file backward compatibility.  No need for FileCheck as the 
+; BitcodeReader will fail with an assert if broken. This test case was 
+; generated using a clang binary, based on LLVM 2.9, downloaded from llvm.org.
+; RUN: llvm-dis < %s.bc > /dev/null
diff --git a/llvm/test/Bitcode/fbench-llvm-2.9.ll.bc b/llvm/test/Bitcode/fbench-llvm-2.9.ll.bc
new file mode 100644
index 00000000000..d2ebbe5c9d7
--- /dev/null
+++ b/llvm/test/Bitcode/fbench-llvm-2.9.ll.bc
diff --git a/llvm/test/Bitcode/spirit-llvm-2.9.ll b/llvm/test/Bitcode/spirit-llvm-2.9.ll
new file mode 100644
index 00000000000..588769159f2
--- /dev/null
+++ b/llvm/test/Bitcode/spirit-llvm-2.9.ll
@@ -0,0 +1,5 @@
+; This isn't really an assembly file. It just runs the test on the bitcode to 
+; ensure bitcode file backward compatibility.  No need for FileCheck as the 
+; BitcodeReader will fail with an assert if broken. This test case was 
+; generated using a clang binary, based on LLVM 2.9, downloaded from llvm.org.
+; RUN: llvm-dis < %s.bc > /dev/null
diff --git a/llvm/test/Bitcode/spirit-llvm-2.9.ll.bc b/llvm/test/Bitcode/spirit-llvm-2.9.ll.bc
new file mode 100644
index 00000000000..bf8cf495d72
--- /dev/null
+++ b/llvm/test/Bitcode/spirit-llvm-2.9.ll.bc