[llvm] [workflows] Add post-commit job that periodically runs the clang static analyzer (PR #94106)
Artem Dergachev via llvm-commits
llvm-commits at lists.llvm.org
Thu Jun 6 12:32:36 PDT 2024
haoNoQ wrote:
The static analyzer is several times more memory-intensive than the compiler, just like it's several times slower than the compiler. But the size of the file is usually not an issue: we deallocate all our analysis-related data structures after every top-level function, going back down to the AST. So if one specific file consumes unusually large amount of memory, it's not because the file is big; it's because one specific function in this file triggers a bug. You can also display all top-level functions with `-Xclang -analyzer-display-progress`. The last one printed is the one in which we got stuck. But this could be too verbose for an everyday buildbot job.
Let me take a look if I can make reproducers work.
https://github.com/llvm/llvm-project/pull/94106
More information about the llvm-commits
mailing list