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
20 lines
863 B
C
20 lines
863 B
C
// 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 escapes(void) {
|
|
// CHECK: <td align="left"><b>Store: </b> <font color="gray">(0x{{[0-9a-f]*}})</font></td>
|
|
// CHECK-SAME: <td align="left">foo</td><td align="left">0</td>
|
|
// CHECK-SAME: <td align="left">&Element\{"foo",0 S64b,char\}</td>
|
|
// CHECK: <td align="left"><b>Expressions: </b></td>
|
|
// CHECK-SAME: <td align="left">"foo"</td>
|
|
// CHECK-SAME: <td align="left">&Element\{"foo",0 S64b,char\}</td>
|
|
const char *const foo = "\x66\x6f\x6f";
|
|
|
|
// CHECK: <font color="cyan4">BinaryOperator</font>
|
|
// CHECK-SAME: <td align="left">1 \| 2</td>
|
|
// CHECK-SAME: <td align="left">3 S32b</td>
|
|
int x = 1 | 2;
|
|
}
|