cppcheck enabled `clang-analyzer-*` clang-tidy warnings

Sep 27 '24 13:09 firewave

As it wrecks havoc on the performance (I did not remember it being so bad) we should limit this to the CI so it won't kill the usability IDEs which support clang-tidy. of

[ 59/240][305.7s] clang-tidy-19 -p=/home/runner/work/cppcheck/cppcheck/cmake.output -quiet /home/runner/work/cppcheck/cppcheck/test/testother.cpp

OTOH it is a bit of relieve to see that other dataflow implementations also seem to struggle with some "heavy" patterns.

Sep 27 '24 14:09 firewave

OTOH it is a bit of relieve to see that other dataflow implementations also seem to struggle with some "heavy" patterns.

It appears they are also slow with big if-else chains.

Oct 18 '24 19:10 firewave

Some of the times are misleading because some of the files are analyzed more than once because of https://github.com/llvm/llvm-project/issues/73357#issuecomment-2080998355.

Oct 18 '24 20:10 firewave

We could run this as a scheduled workflow.

Jan 28 '25 21:01 firewave

I filed https://github.com/llvm/llvm-project/issues/132001 about the clang-analyzer-optin.cplusplus.UninitializedObject false positives with unnamed fields used for explicit padding.

Mar 19 '25 10:03 firewave

I will adjust this so there will be an additional target for the static analyzer.

Mar 19 '25 10:03 firewave

It would be great to have a badge for this run on the main page but I have no idea how to differentiate the scheduled run from a regular one.

Mar 19 '25 19:03 firewave