Previously, when using `-analyze-function` to target a specific function, the analyzer would incorrectly report "Every top-level function was skipped" even when the function was successfully analyzed by syntax-only checkers. This happened because `NumFunctionsAnalyzed` only counted path-sensitive analysis, not syntax-only analysis. The misuse detection logic would see 0 functions analyzed and incorrectly conclude the function wasn't found.
63 lines
2.9 KiB
C++
63 lines
2.9 KiB
C++
int fizzbuzz(int x, bool y) {
|
|
return x + y;
|
|
}
|
|
|
|
// C++ but not uses parentheses in the '-analyze-function' option.
|
|
//
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core \
|
|
// RUN: -analyze-function='missing_fn' -x c++ \
|
|
// RUN: -triple x86_64-pc-linux-gnu 2>&1 %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-CXX
|
|
//
|
|
// CHECK-CXX: Every top-level function was skipped.
|
|
// CHECK-CXX-NEXT: Pass the -analyzer-display-progress for tracking which functions are analyzed.
|
|
// CHECK-CXX-NEXT: For analyzing C++ code you need to pass the function parameter list: -analyze-function="foobar(int, _Bool)"
|
|
|
|
// C but uses parentheses in the '-analyze-function' option.
|
|
//
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core \
|
|
// RUN: -analyze-function='missing_fn()' -x c -Dbool=_Bool \
|
|
// RUN: -triple x86_64-pc-linux-gnu 2>&1 %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-C
|
|
//
|
|
// CHECK-C: Every top-level function was skipped.
|
|
// CHECK-C-NEXT: Pass the -analyzer-display-progress for tracking which functions are analyzed.
|
|
// CHECK-C-NEXT: For analyzing C code you shouldn't pass the function parameter list, only the name of the function: -analyze-function=foobar
|
|
|
|
// The user passed the '-analyzer-display-progress' option, we don't need to advocate it.
|
|
//
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core \
|
|
// RUN: -analyze-function=missing_fn \
|
|
// RUN: -analyzer-display-progress -x c -Dbool=_Bool \
|
|
// RUN: -triple x86_64-pc-linux-gnu 2>&1 %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-DONT-ADVOCATE-DISPLAY-PROGRESS
|
|
//
|
|
// CHECK-DONT-ADVOCATE-DISPLAY-PROGRESS: Every top-level function was skipped.
|
|
// CHECK-DONT-ADVOCATE-DISPLAY-PROGRESS-NOT: Pass the -analyzer-display-progress
|
|
|
|
// The user passed the '-analyze-function' option but that doesn't mach to any declaration.
|
|
//
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core \
|
|
// RUN: -analyze-function='missing_fn()' -x c++ \
|
|
// RUN: -triple x86_64-pc-linux-gnu 2>&1 %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-ADVOCATE-DISPLAY-PROGRESS
|
|
//
|
|
// CHECK-ADVOCATE-DISPLAY-PROGRESS: Every top-level function was skipped.
|
|
// CHECK-ADVOCATE-DISPLAY-PROGRESS-NEXT: Pass the -analyzer-display-progress for tracking which functions are analyzed.
|
|
// CHECK-ADVOCATE-DISPLAY-PROGRESS-NOT: For analyzing
|
|
|
|
// The user only enables syntax-only analysis, like `debug.DumpDominators`.
|
|
// `-analyze-function` should only match the given function.
|
|
//
|
|
// RUN: %clang_analyze_cc1 -analyzer-checker=core,debug.DumpDominators -analyzer-config ipa=none \
|
|
// RUN: -analyze-function='fizzbuzz(int, _Bool)' -x c++ \
|
|
// RUN: -triple x86_64-pc-linux-gnu 2>&1 %s \
|
|
// RUN: | FileCheck %s -check-prefix=CHECK-SYNTAX-ONLY --allow-empty
|
|
//
|
|
// With syntax-only analysis, the function is found and analyzed, so no error message.
|
|
// CHECK-SYNTAX-ONLY: Immediate dominance tree (Node#,IDom#):
|
|
// CHECK-SYNTAX-ONLY-NEXT: (0,1)
|
|
// CHECK-SYNTAX-ONLY-NEXT: (1,2)
|
|
// CHECK-SYNTAX-ONLY-NEXT: (2,2)
|
|
// CHECK-SYNTAX-ONLY-NOT: Every top-level function was skipped.
|