https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613

--- Comment #19 from Kamil Dudka <kdudka at redhat dot com> ---
Thank you for working on this!  I really like the gcc-latest COPR, which makes
it easy to test the changes.  I spotted that man pages installed by gcc-latest
are broken but that is a cosmetic issue.

I have hacked up a quick and dirty patch to make csmock-plugin-gcc use this,
tested it on the units and curl RPM packages and it seemed to work fine:
https://github.com/csutils/csmock/pull/187

I needed to suppress the diagnostics output printed by gcc to stderr so that
csmock does not capture the same information twice using two different formats.
 I was able to get around with `-fdiagnostics-format=json-file` but it
wastefully creates files that are not used for anything.

Is there a better way to tell gcc to write all diagnostic messages only to the
specified SARIF file while keeping messages about unsupported flags,
non-existing input files and the like still printed to stderr?

Reply via email to