public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 7b4f92f0f5b11e412c91f563c2f7380830a4610c Date: Mon, 20 Apr 2020 22:05:23 +0000 (GMT) [thread overview] Message-ID: <20200420220523.60A0B384A87E@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 7b4f92f0f5b11e412c91f563c2f7380830a4610c (commit) from e7e729ae2b8cc9861ce0351a8fd7e3095c20ff71 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 7b4f92f0f5b11e412c91f563c2f7380830a4610c Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Apr 16 19:07:43 2020 -0400 wwwdocs: document my changes for gcc 10 diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 65e2fb3d..fc8f16e7 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -98,6 +98,14 @@ a work-in-progress.</p> This makes it possible to rebuild program with same outcome which is useful, for example, for distribution packages. </li> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + enables a new static analysis pass and associated warnings. + This pass performs a time-consuming exploration of paths through + the code in the hope of detecting various common errors, such as + double-free bugs. This option should be regarded as + <b>experimental</b> in this release. In particular, analysis of non-C + code is unlikely to work. + </li> </ul> </li> <li> @@ -860,7 +868,23 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); <!-- .................................................................. --> -<!-- <h2 id="plugins">Improvements for plugin authors</h2> --> +<h2 id="plugins">Improvements for plugin authors</h2> +<ul> + <li> + GCC diagnostics can now have a chain of events associated with them, + describing a path through the code that triggers the problem. + These can be printed by the diagnostics subsystem in various ways, + controlled by the + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-path-format">-fdiagnostics-path-format</a> + option, or captured in JSON form via + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format">-fdiagnostics-format=json</a>.</li> + <li> + GCC diagnostics can now be associated with + <a href="https://cwe.mitre.org">CWE weakness identifiers</a>, which + will appear on the standard error stream, and in the JSON output from + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format">-fdiagnostics-format=json</a>. + </li> +</ul> <!-- .................................................................. --> <h2>Other significant improvements</h2> @@ -873,9 +897,18 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); for overlapping memory moves, consistent with the library functions <code>memcpy</code> and <code>memmove</code>. </li> + <li> + For many releases, when GCC emits a warning it prints the option + controlling that warning. As of GCC 10, that option text is now a + clickable hyperlink for the documentation of that option (assuming a + <a href="https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda">sufficiently capable terminal</a>). + This behavior can be controlled via a new + <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-urls">-fdiagnostics-urls</a> + option (along with various environment variables and heuristics + documented with that option). + </li> </ul> - <!-- .................................................................. --> <!-- <h2><a name="10.1">GCC 10.1</a></h2> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 37 +++++++++++++++++++++++++++++++++++-- 1 file changed, 35 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-20 22:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200420220523.60A0B384A87E@sourceware.org \ --to=dmalcolm@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).