Added AnalyzerStatsChecker, a path sensitive check that reports visitation statistics about analysis. Running clang with the -analyzer-stats flag will emit warnings containing the information. We can then run a postanalysis script to take this data and give useful information about how much the analyzer missed in a project.
llvm-svn: 113568
This commit is contained in:
@@ -99,6 +99,8 @@ static void AnalyzerOptsToArgs(const AnalyzerOptions &Opts,
|
||||
Res.push_back("-analyzer-display-progress");
|
||||
if (Opts.AnalyzeNestedBlocks)
|
||||
Res.push_back("-analyzer-opt-analyze-nested-blocks");
|
||||
if (Opts.AnalyzerStats)
|
||||
Res.push_back("-analyzer-stats");
|
||||
if (Opts.EagerlyAssume)
|
||||
Res.push_back("-analyzer-eagerly-assume");
|
||||
if (!Opts.PurgeDead)
|
||||
@@ -815,6 +817,7 @@ static void ParseAnalyzerArgs(AnalyzerOptions &Opts, ArgList &Args,
|
||||
Opts.AnalyzerDisplayProgress = Args.hasArg(OPT_analyzer_display_progress);
|
||||
Opts.AnalyzeNestedBlocks =
|
||||
Args.hasArg(OPT_analyzer_opt_analyze_nested_blocks);
|
||||
Opts.AnalyzerStats = Args.hasArg(OPT_analysis_AnalyzerStats);
|
||||
Opts.PurgeDead = !Args.hasArg(OPT_analyzer_no_purge_dead);
|
||||
Opts.EagerlyAssume = Args.hasArg(OPT_analyzer_eagerly_assume);
|
||||
Opts.AnalyzeSpecificFunction = Args.getLastArgValue(OPT_analyze_function);
|
||||
|
||||
Reference in New Issue
Block a user