forked from OSchip/llvm-project
[analyzer] Don't print the config count in debug.ConfigDumper
I think anyone who added a checker config wondered why is there a need to test this. Its just a chore when adding a new config, so I removed it. To give some historic insight though, we used to not list **all** options, but only those explicitly added to AnalyzerOptions, such as the ones specified on the command line. However, past this change (and arguably even before that) this line makes little sense. There is an argument to be made against the entirety of analyzer-config.c test file, but since this commit fixes some builtbots and is landing without review, I wouldn't like to be too invasive.
This commit is contained in:
parent
5bc0c8f009
commit
268fa40daa
|
@ -281,8 +281,6 @@ public:
|
|||
llvm::errs() << Keys[I]->getKey() << " = "
|
||||
<< (Keys[I]->second.empty() ? "\"\"" : Keys[I]->second)
|
||||
<< '\n';
|
||||
|
||||
llvm::errs() << "[stats]\n" << "num-entries = " << Keys.size() << '\n';
|
||||
}
|
||||
};
|
||||
}
|
||||
|
|
|
@ -107,5 +107,3 @@
|
|||
// CHECK-NEXT: unix.DynamicMemoryModeling:Optimistic = false
|
||||
// CHECK-NEXT: unroll-loops = false
|
||||
// CHECK-NEXT: widen-loops = false
|
||||
// CHECK-NEXT: [stats]
|
||||
// CHECK-NEXT: num-entries = 104
|
||||
|
|
Loading…
Reference in New Issue