Cppcheck has a very useful option: --cppcheck-build-dir. According to --help, one advantage of this option is:
fasteranalysis; Cppcheck will reuse the results ifthehashforafileisunchanged.
And indeed, when we run Cppcheck 2.14.2 on our whole project with --cppcheck-build-dir, the first time takes about 14 minutes, but if we run Cppcheck again with --cppcheck-build-dir without making any changes to the code to be analyzed, it now takes only about 1 minute.
With Cppcheck 2.18.0, however, we do not observe any speed-up. Running Cppcheck on our whole project with --cppcheck-build-dir takes about 15 minutes the first time, and also the second time.
I didn't try with versions between 2.14.2 and 2.18.0.
Is this a known regression?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cppcheck has a very useful option:
--cppcheck-build-dir
. According to--help
, one advantage of this option is:And indeed, when we run Cppcheck 2.14.2 on our whole project with
--cppcheck-build-dir
, the first time takes about 14 minutes, but if we run Cppcheck again with--cppcheck-build-dir
without making any changes to the code to be analyzed, it now takes only about 1 minute.With Cppcheck 2.18.0, however, we do not observe any speed-up. Running Cppcheck on our whole project with
--cppcheck-build-dir
takes about 15 minutes the first time, and also the second time.I didn't try with versions between 2.14.2 and 2.18.0.
Is this a known regression?
Thanks for reporting, ticket is here: https://trac.cppcheck.net/ticket/14064