aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorKirstóf Umann <dkszelethus@gmail.com>2020-05-19 16:46:16 +0200
committerKirstóf Umann <dkszelethus@gmail.com>2020-05-19 16:51:14 +0200
commit268fa40daa151d3b4bff1df12b62e5dae94685d7 (patch)
tree26847719b781945e6e12270db8d8e4541f0e1710 /clang/lib/Frontend/CompilerInvocation.cpp
parent5bc0c8f009261425a25c1bb109f81b454c928bf5 (diff)
downloadllvm-268fa40daa151d3b4bff1df12b62e5dae94685d7.zip
llvm-268fa40daa151d3b4bff1df12b62e5dae94685d7.tar.gz
llvm-268fa40daa151d3b4bff1df12b62e5dae94685d7.tar.bz2
[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.
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions