llvm-project/clang/test/Analysis/aggrinit-cfg-output.cpp
Donát Nagy c3f8dd1228
[NFC][analyzer] Use %clang_analyze_cc1 consistently (#145895)
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
2025-06-30 12:59:51 +02:00

29 lines
741 B
C++

// RUN: %clang_analyze_cc1 -analyzer-checker=debug.DumpCFG -analyzer-config cfg-expand-default-aggr-inits=true %s > %t 2>&1
// RUN: FileCheck --input-file=%t %s
static char a[] = "foobar";
struct StringRef {
const char *member = nullptr;
int len = 3;
};
int main() {
StringRef s{a};
(void)s;
}
// CHECK: [B1]
// CHECK-NEXT: 1: a
// CHECK-NEXT: 2: [B1.1] (ImplicitCastExpr, ArrayToPointerDecay, char *)
// CHECK-NEXT: 3: [B1.2] (ImplicitCastExpr, NoOp, const char *)
// CHECK-NEXT: 4: 3
// CHECK-NEXT: 5:
// CHECK-NEXT: 6: {[B1.1]}
// CHECK-NEXT: 7: StringRef s{a};
// CHECK-NEXT: 8: s
// CHECK-NEXT: 9: (void)[B1.8] (CStyleCastExpr, ToVoid, void)
// CHECK-NEXT: Preds (1): B2
// CHECK-NEXT: Succs (1): B0