public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 045b04486fbc6b88eed5e1d21b2c0a2d94649d63 Date: Wed, 23 Dec 2020 12:44:25 +0000 (GMT) [thread overview] Message-ID: <20201223124425.7ED913851C04@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 045b04486fbc6b88eed5e1d21b2c0a2d94649d63 (commit) from 05c170a452a9aecf36a719515a7e64f7999305e4 (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 045b04486fbc6b88eed5e1d21b2c0a2d94649d63 Author: Martin Liska <mliska@suse.cz> Date: Wed Dec 23 13:44:17 2020 +0100 Document my changes. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index d04b377d..f457b7e7 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -168,6 +168,12 @@ a work-in-progress.</p> <h3 id="c-family">C family</h3> <ul> + <li>New attribute: + <ul> + <li>The <code>no_stack_protector</code> attribute has been added to mark functions which should not be instrumented + with stack protection (<code>-fstack-protector</code>).</li> + </ul> + </li> <li>New warnings: <ul> <li><code>-Wsizeof-array-div</code>, enabled by <code>-Wall</code>, warns @@ -193,6 +199,28 @@ a work-in-progress.</p> This functionality requires Binutils version 2.36 or later. </p> </li> + <li>A new warning <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wtsan"><code>-Wtsan</code></a>, enabled by default, + warns about unsupported features in ThreadSanitizer (currently <code>std::atomic_thread_fence</code>).</li> + <li>A series of conditional expressions that compare the same variable can be transformed into a switch statement + if each of them contains a comparison expression. Example: + <pre> + int IsHTMLWhitespace(int aChar) { + return aChar == 0x0009 || aChar == 0x000A || + aChar == 0x000C || aChar == 0x000D || + aChar == 0x0020; + } + </pre> + This statement can be transformed into a switch statement and then expanded into a bit-test. + </li> + <li> + New command-line options: + <ul> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#index-fno-bit-tests"><code>-fbit-tests</code></a>, enabled by default, can be used to enable or disable switch expansion using bit-tests.</li> + </ul> + </li> + <li>GCOV data file format outputs smaller files by representing zero counters in a more compact way.</li> + <li>Some short options of the <code>gcov</code> tool have been renamed: <code>-i</code> to <code>-j</code> + and <code>-j</code> to <code>-H</code>.</li> </ul> <h3 id="cxx">C++</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-12-23 12:44 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=20201223124425.7ED913851C04@sourceware.org \ --to=marxin@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).