summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlp Toker <alp@nuanti.com>2014-06-27 02:04:28 +0000
committerAlp Toker <alp@nuanti.com>2014-06-27 02:04:28 +0000
commit1a5a520d9555680898b6112bf6a601ceb85c300d (patch)
treebc732a2382d1a00f64591b09cf0950273bb76928
parentaab3a8f2fb793891f7597e1fdd7edce488530ddd (diff)
downloadbcm5719-llvm-1a5a520d9555680898b6112bf6a601ceb85c300d.tar.gz
bcm5719-llvm-1a5a520d9555680898b6112bf6a601ceb85c300d.zip
Add test coverage for .bc input in the frontend
Test that we can consume LLVM bitcode and additionally check that it produces the same output as a direct compilation. The feature is crashy and has gone untested until now, but we might as well provide some coverage as long as it remains in tree. Also test LL source input in the same way because the existing tests for that don't look convincing. llvm-svn: 211844
-rw-r--r--clang/test/Frontend/ir-support.c17
1 files changed, 17 insertions, 0 deletions
diff --git a/clang/test/Frontend/ir-support.c b/clang/test/Frontend/ir-support.c
new file mode 100644
index 00000000000..3e1089b965e
--- /dev/null
+++ b/clang/test/Frontend/ir-support.c
@@ -0,0 +1,17 @@
+// Test that we can consume LLVM IR/bitcode in the frontend and produce
+// identical output to a standard compilation.
+
+// Reference output:
+// RUN: %clang_cc1 -S -o %t.s %s
+
+// LLVM bitcode:
+// RUN: %clang_cc1 -emit-llvm-bc -o %t.bc %s
+// RUN: %clang_cc1 -S -o - %t.bc > %t.bc.s
+// RUN: diff %t.s %t.bc.s
+
+// LLVM IR source code:
+// RUN: %clang_cc1 -emit-llvm-bc -o %t.ll %s
+// RUN: %clang_cc1 -S -o - %t.ll > %t.ll.s
+// RUN: diff %t.s %t.ll.s
+
+int f() { return 0; }
OpenPOWER on IntegriCloud