
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
32 lines
857 B
C++
32 lines
857 B
C++
// RUN: %clang_analyze_cc1 -analyzer-checker=debug.AnalysisOrder -analyzer-config debug.AnalysisOrder:Bind=true -analyzer-config debug.AnalysisOrder:RegionChanges=true %s 2>&1 | FileCheck %s
|
|
|
|
struct Super {
|
|
virtual void m();
|
|
};
|
|
struct Sub : Super {
|
|
virtual void m() {}
|
|
};
|
|
|
|
void testTemporaries() {
|
|
// This triggers RegionChanges once for zero-initialization of the structure.
|
|
Sub().m();
|
|
}
|
|
|
|
void seeIfCheckBindWorks() {
|
|
// This should trigger checkBind. The rest of the code shouldn't.
|
|
// This also triggers checkRegionChanges after that.
|
|
// Note that this function is analyzed first, so the messages would be on top.
|
|
int x = 1;
|
|
}
|
|
|
|
// seeIfCheckBindWorks():
|
|
// CHECK: Bind
|
|
// CHECK-NEXT: RegionChanges
|
|
|
|
// testTemporaries():
|
|
// CHECK-NEXT: RegionChanges
|
|
|
|
// Make sure there's no further output.
|
|
// CHECK-NOT: Bind
|
|
// CHECK-NOT: RegionChanges
|