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
27 lines
818 B
C++
27 lines
818 B
C++
// CAUTION: The name of this file should start with `l` for proper tests.
|
|
// RUN: %clang_analyze_cc1 -triple x86_64-unknown-linux-gnu \
|
|
// RUN: -analyzer-checker=core \
|
|
// RUN: -analyzer-dump-egraph=%t.dot %s
|
|
// RUN: %exploded_graph_rewriter %t.dot | FileCheck %s
|
|
|
|
void test1() {
|
|
// Here __FILE__ macros produces a string with `\` delimiters on Windows
|
|
// and the name of the file starts with `l`.
|
|
char text[] = __FILE__;
|
|
}
|
|
|
|
void test2() {
|
|
// Here `\l` is in the middle of the literal.
|
|
char text[] = "string\\literal";
|
|
}
|
|
|
|
void test() {
|
|
test1();
|
|
test2();
|
|
}
|
|
|
|
// This test is passed if exploded_graph_rewriter handles dot file without errors.
|
|
// CHECK: digraph "ExplodedGraph"
|
|
// CHECK: shape=record,label=<<table border="0">
|
|
// CHECK: char text[] = "string\\literal";
|