https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102471
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> --- I've created https://github.com/davidmalcolm/gcc-analyzer-integration-tests which builds Juliet plus various real-world C projects with a candidate build of GCC with -fanalyzer and captures the diagnostics in SARIF format. https://github.com/microsoft/sarif-tools has a command for comparing SARIF files (or pairs of directories full of SARIF files) which is what I'm currently using to compare diagnostics emitted before/after a candidate GCC patch. I'm working through the diagnostics seen with GCC trunk's -fanalyzer, classifying them into true vs false positives and will probably write my own comparison script to show the effect of a GCC patch on false vs true positives.
