c3f8dd1228
A large majority of the LIT tests of the clang static analyzer use RUN lines with the placeholder `%clang_analyze_cc1` which expands to `%clang_cc1 -analyze -setup-static-analyzer` where the only effect of `-setup-static-analyzer` is that it ensures that the macro `__clang_analyzer__` is defined. However, there were some tests that used `%clang_cc1 -analyze` directly; this commit changes those to using `%clang_analyze_cc1` for the sake of consistency. Previously `%clang_analyze_cc1` did not work within the directory `exploded-graph-rewriter` (because that directory has its own custom `lit.local.cfg`) but this problem was eliminated by the recent commit 40cc4379cda6e0d6efe72c55d1968f9cf427a16a, so it was possible to resolve and delete the FIXME comments asking for this change. There are a few tests that use `%clang --analyze` or other command-line flags (e.g. help flags), those are not affected by this change. This cleanup was discussed in the discourse thread https://discourse.llvm.org/t/taking-ownership-of-clang-test-analysis/84689/11
23 lines
862 B
C
23 lines
862 B
C
// RUN: rm -rf %t && mkdir %t
|
|
// RUN: mkdir -p %t/ctudir2
|
|
// RUN: %clang_cc1 \
|
|
// RUN: -emit-pch -o %t/ctudir2/ctu-import.c.ast %S/Inputs/ctu-import.c
|
|
// RUN: cp %S/Inputs/ctu-import.c.externalDefMap.ast-dump.txt %t/ctudir2/externalDefMap.txt
|
|
// RUN: %clang_analyze_cc1 \
|
|
// RUN: -analyzer-checker=core,debug.ExprInspection \
|
|
// RUN: -analyzer-config eagerly-assume=false \
|
|
// RUN: -analyzer-config experimental-enable-naive-ctu-analysis=true \
|
|
// RUN: -analyzer-config display-ctu-progress=true \
|
|
// RUN: -analyzer-config ctu-dir=%t/ctudir2 \
|
|
// RUN: -verify %s
|
|
|
|
void clang_analyzer_eval(int);
|
|
|
|
int testStaticImplicit(void);
|
|
int func(void) {
|
|
int ret = testStaticImplicit();
|
|
clang_analyzer_eval(ret == 4); // expected-warning{{TRUE}} ctu
|
|
// expected-warning@-1{{UNKNOWN}} stu
|
|
return testStaticImplicit();
|
|
}
|