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. 752e29ec094f9df75b158eb40db44265345b1a3f Date: Mon, 16 Nov 2020 23:27:16 +0000 (GMT) [thread overview] Message-ID: <20201116232716.CF33B385780A@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 752e29ec094f9df75b158eb40db44265345b1a3f (commit) via dc256980746c184b91b168604a3674af8f633217 (commit) from 8324ef5943ff70ff1a7786f3d580be8cfe6edf99 (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 752e29ec094f9df75b158eb40db44265345b1a3f Author: David Malcolm <dmalcolm@redhat.com> Date: Mon Nov 16 18:24:20 2020 -0500 gcc-11/changes: Document analyzer changes diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 21d59f51..46a6a372 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -378,6 +378,38 @@ a work-in-progress.</p> <!-- <h2>Documentation improvements</h2> --> +<!-- .................................................................. --> +<h2 id="analyzer">Improvements to Static Analyzer</h2> +<ul> + <li>The implementation of how program state is tracked within + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + has been completely rewritten for GCC 11, fixing numerous bugs, and + allowing for the analyzer to scale to larger C source files. + </li> + <li>As preliminary work towards eventually supporting C++, the + <code>malloc</code>/<code>free</code> checking within + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + has been generalized to also check <code>new</code>/<code>delete</code> + and <code>new[]</code>/<code>delete[]</code>, adding a new + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-mismatching-deallocation">-Wanalyzer-mismatching-deallocation</a> + warning. However, C++ is not yet properly supported by + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + (for example, exception-handling is unimplemented).</li> + <li>The analyzer has gained warnings + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-negative">-Wanalyzer-shift-count-negative</a>, + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-shift-count-overflow">-Wanalyzer-shift-count-overflow</a>, + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-const">-Wanalyzer-write-to-const</a>, and + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-write-to-string-literal">-Wanalyzer-write-to-string-literal</a>, + all enabled by default when + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html">-fanalyzer</a> + is enabled. + </li> + <li>The analyzer has gained new debugging options + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fdump-analyzer-json">-fdump-analyzer-json</a> and + <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fno-analyzer-feasibility">-fno-analyzer-feasibility</a>. + </li> +</ul> + <!-- .................................................................. --> <!-- <h2 id="plugins">Improvements for plugin authors</h2> --> commit dc256980746c184b91b168604a3674af8f633217 Author: David Malcolm <dmalcolm@redhat.com> Date: Mon Nov 16 16:20:15 2020 -0500 gcc-11/changes: Document libgccjit changes diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 798257aa..21d59f51 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -240,7 +240,19 @@ a work-in-progress.</p> <!-- <h3 id="go">Go</h3> --> <!-- .................................................................. --> -<!-- <h2 id="jit">libgccjit</h2> --> +<h2 id="jit">libgccjit</h2> +<ul> + <li>libgccjit can now be built for MinGW</li> + <li> + The libgccjit API gained 10 new entry points: + <ul> + <li> + <a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_global_set_initializer">gcc_jit_global_set_initializer</a> + </li> + <li>9 entrypoints for <a href="https://gcc.gnu.org/onlinedocs/jit/topics/asm.html">directly embedding asm statements into a compile</a>, analogous to inline <code>asm</code> in the C frontend</li> + </ul> + </li> +</ul> <!-- .................................................................. --> <h2 id="targets">New Targets and Target Specific Improvements</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 46 +++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-11-16 23:27 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=20201116232716.CF33B385780A@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).