Signed-off-by: David Malcolm <dmalc...@redhat.com> --- htdocs/gcc-14/changes.html | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+)
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index d782c334..934cd1ad 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -922,6 +922,28 @@ it emits: </li> </ul> +<!-- .................................................................. --> +<h2 id="sarif">Improvements to SARIF support</h2> +<ul> + <li> + <!-- commit r14-6228-g3bd8241a1f1982 --> + The SARIF output from + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format";>-fdiagnostics-format=</code></a> + now adds indentation and newlines to reflect the logical JSON structure of the data. The previous compact behavior can be restored via the new option + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-json-formatting";>-fno-diagnostics-json-formatting</code></a>. + This also applies to the older output format named "json". + </li> + <li> + <!-- commit r14-2881-g75d623946d4b6e [PR109361] --> + If profiling information about the compiler itself is requested via + <a href="https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-ftime-report";>-ftime-report</code></a>, + and a SARIF output format is requested via + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format";>-fdiagnostics-format=</code></a>, + then the timing and memory usage data is now written in JSON form into + the SARIF output, rather than as plain text to stderr. + </li> +</ul> + <!-- .................................................................. --> <h2 id="plugins">Improvements for plugin authors</h2> <ul> -- 2.39.2
