4 ms·
At LibreOffice we, (mostly I) do whole program analyses, and they are fairly useful e.g. https://cgit.freedesktop.org/libreoffice/core/tree/compilerplugins
by grandinj 8y ago
At LibreOffice we, (mostly I) do whole program analyses, and they are fairly useful
e.g.
https://cgit.freedesktop.org/libreoffice/core/tree/compilerplugins/clang/constantparam.cxx https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...
That said, the analyses
(a) are specific to our team
(b) require about 2 hours (each) to compute on a 6-core box
(c) are only run every couple of months
(d) are run and applied by the same person.
(e) have a false positive rate of around 1%, so require manual review
(f) often make assumptions that are only valid for how we use C++ and various libraries (without some "well just don't do that" assumptions you can't do any useful analysis across a C++ codebase :-)
- skylyrac 8y agoWe use Coverity and, even though some members of the team really dislike it, I think it is quite helpful to detect things that would go unnoticed otherwise. However, our project is relatively small, so we are normally done in ~15 minutes. We run it right before upstreaming patches, which means that the tests run once or twice a day.