summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorge Burgess IV <george.burgess.iv@gmail.com>2017-08-09 05:20:05 +0000
committerGeorge Burgess IV <george.burgess.iv@gmail.com>2017-08-09 05:20:05 +0000
commit8b928feeb4d7b945302c7fc906d6722f512391cc (patch)
tree67828cce2f6a45326202ccfe45a40efefb04b1af
parent6ea2e81cf64b4362a22e8a64a61d3c29709b0d9b (diff)
downloadbcm5719-llvm-8b928feeb4d7b945302c7fc906d6722f512391cc.tar.gz
bcm5719-llvm-8b928feeb4d7b945302c7fc906d6722f512391cc.zip
Attempt to appease msc buildbot
It was timing out on this test, but for reasons unrelated to the specific bug it was testing for. Randomly breaking in gdb with `clang -target i686-windows -fmsc-version=1700` reveals *many* frames from MicrosoftCXXNameMangler. So, it would seem that some caching is needed there, as well... Fingers crossed that specifying a triple is sufficient to work around this. llvm-svn: 310444
-rw-r--r--clang/test/CodeGenCXX/pr29160.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/test/CodeGenCXX/pr29160.cpp b/clang/test/CodeGenCXX/pr29160.cpp
index 9c9238e8a0b..1db48a34e01 100644
--- a/clang/test/CodeGenCXX/pr29160.cpp
+++ b/clang/test/CodeGenCXX/pr29160.cpp
@@ -1,4 +1,4 @@
-// RUN: %clang_cc1 -std=c++11 %s -o /dev/null -S
+// RUN: %clang_cc1 -std=c++11 -triple i686-linux %s -o /dev/null -S
//
// This test's failure mode is running ~forever. (For some value of "forever"
// that's greater than 25 minutes on my machine)
OpenPOWER on IntegriCloud