summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMehdi Amini <mehdi.amini@apple.com>2016-04-24 03:44:55 +0000
committerMehdi Amini <mehdi.amini@apple.com>2016-04-24 03:44:55 +0000
commit5655795bf4acb155b37bd94ee991980526179a61 (patch)
tree6517f89dac2089cdc7828a5c7be87a8fea63bde3
parent971481db982d36338cbb2c096e98576dc5de2edc (diff)
downloadbcm5719-llvm-5655795bf4acb155b37bd94ee991980526179a61.tar.gz
bcm5719-llvm-5655795bf4acb155b37bd94ee991980526179a61.zip
Make thinlto clang test more robust against LLVM changes.
We should just test the effect of the clang level option here, i.e. that a summary is correctly emitted with -flto=thin From: Mehdi Amini <mehdi.amini@apple.com> llvm-svn: 267321
-rw-r--r--clang/test/Misc/thinlto.c9
1 files changed, 2 insertions, 7 deletions
diff --git a/clang/test/Misc/thinlto.c b/clang/test/Misc/thinlto.c
index ae2c148890d..ec0f03f5a2a 100644
--- a/clang/test/Misc/thinlto.c
+++ b/clang/test/Misc/thinlto.c
@@ -1,9 +1,4 @@
// RUN: %clang_cc1 -flto=thin -emit-llvm-bc < %s | llvm-bcanalyzer -dump | FileCheck %s
+// ; Check that the -flto=thin option emits a summary
// CHECK: <GLOBALVAL_SUMMARY_BLOCK
-// CHECK-NEXT: <PERMODULE
-// CHECK-NEXT: <PERMODULE
-// CHECK-NEXT: </GLOBALVAL_SUMMARY_BLOCK
-
-__attribute__((noinline)) void foo() {}
-
-int main() { foo(); }
+int main() {}
OpenPOWER on IntegriCloud