summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorge Burgess IV <george.burgess.iv@gmail.com>2019-08-05 23:19:15 +0000
committerGeorge Burgess IV <george.burgess.iv@gmail.com>2019-08-05 23:19:15 +0000
commita5c25c5d469f0f9999610bb391bd156eb70e7975 (patch)
tree21508c23bba7585dfb3f8fe16e2cbc7be92e8d8f
parentd32d5db4daca6380d0a36338ecbab6df4b0bc585 (diff)
downloadbcm5719-llvm-a5c25c5d469f0f9999610bb391bd156eb70e7975.tar.gz
bcm5719-llvm-a5c25c5d469f0f9999610bb391bd156eb70e7975.zip
[Sema] attempt to appease buildbots after r367940
A buildbot got angry about this new test, with error messages like: warn-nullchar-nullptr.c Line 16: use of undeclared identifier 'u' It looks like this `u'c'` syntax was introduced in C11; I'm guessing some bots may default to something before that. Let's see if explicitly specifying the standard version makes it happy... llvm-svn: 367947
-rw-r--r--clang/test/Sema/warn-nullchar-nullptr.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/test/Sema/warn-nullchar-nullptr.c b/clang/test/Sema/warn-nullchar-nullptr.c
index 36a126a0433..eabfebc266d 100644
--- a/clang/test/Sema/warn-nullchar-nullptr.c
+++ b/clang/test/Sema/warn-nullchar-nullptr.c
@@ -1,4 +1,4 @@
-// RUN: %clang_cc1 -fsyntax-only -verify -Wall %s
+// RUN: %clang_cc1 -fsyntax-only -verify -Wall %s -std=c11
int test1(int *a) {
return a == '\0'; // expected-warning {{comparing a pointer to a null character constant; did you mean to compare to (void *)0?}}
OpenPOWER on IntegriCloud