-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
base: main
Are you sure you want to change the base?
Conversation
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.
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. |
Some of the times are misleading because some of the files are analyzed more than once because of llvm/llvm-project#73357 (comment). |
a8f5bbd
to
532ef91
Compare
We could run this as a scheduled workflow. |
5f60dc7
to
0828a83
Compare
clang-analyzer-*
clang-tidy warningsclang-tidy
analysis with clang-analyzer-*
warnings enabled
de3f6fe
to
3811247
Compare
3811247
to
8e49309
Compare
240a115
to
1af19f2
Compare
No description provided.