Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perform scheduled clang-tidy analysis with clang-analyzer-* warnings enabled #6835

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

firewave
Copy link
Collaborator

No description provided.

@firewave
Copy link
Collaborator Author

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.

@firewave
Copy link
Collaborator Author

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.

@firewave
Copy link
Collaborator Author

firewave commented Oct 18, 2024

Some of the times are misleading because some of the files are analyzed more than once because of llvm/llvm-project#73357 (comment).

@firewave
Copy link
Collaborator Author

We could run this as a scheduled workflow.

@firewave firewave force-pushed the ci-tidy-static branch 2 times, most recently from 5f60dc7 to 0828a83 Compare January 28, 2025 21:46
@firewave firewave changed the title enabled clang-analyzer-* clang-tidy warnings perform scheduled clang-tidy analysis with clang-analyzer-* warnings enabled Jan 28, 2025
@firewave firewave force-pushed the ci-tidy-static branch 2 times, most recently from de3f6fe to 3811247 Compare January 28, 2025 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant