public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <msebor@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 5a57e261bcfbb7691901bdf219ba114b449b690e
Date: Wed, 10 Feb 2021 00:45:24 +0000 (GMT)	[thread overview]
Message-ID: <20210210004524.AD1963858D29@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  5a57e261bcfbb7691901bdf219ba114b449b690e (commit)
      from  cf0d4e41a94bae204a8c5d2490063d58cdb1d4e3 (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 5a57e261bcfbb7691901bdf219ba114b449b690e
Author: Martin Sebor <msebor@redhat.com>
Date:   Tue Feb 9 17:40:01 2021 -0700

    Move -Wtsan under New Warnings.  Add more links to the user manual.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 80d39b73..de75b8d6 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -174,7 +174,8 @@ a work-in-progress.</p>
 <ul>
   <li>New attributes:
     <ul>
-        <li>The <code>no_stack_protector</code> attribute has been added to mark functions which should not be instrumented
+      <li>The <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-no_005fstack_005fprotector-function-attribute"><code>no_stack_protector</code></a>
+	attribute has been added to mark functions which should not be instrumented
             with stack protection (<code>-fstack-protector</code>).</li>
 	<li>The existing
 	  <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-malloc-function-attribute"><code>malloc</code></a>
@@ -205,6 +206,10 @@ a work-in-progress.</p>
 	GCC releases most instances of his warning are diagnosed by
 	<code>-Wstringop-overflow</code>.
       </li>
+      <li><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>
     </ul>
   </li>
   <li>Enhancements to existing warnings:
@@ -238,8 +243,6 @@ 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>
@@ -376,19 +379,23 @@ a work-in-progress.</p>
       (<a href="https://gcc.gnu.org/PR97518">PR97518</a>).</li>
   <li>New warnings:
     <ul>
-      <li><code>-Wctad-maybe-unsupported</code>, disabled by default, warns
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wctad-maybe-unsupported"><code>-Wctad-maybe-unsupported</code></a>,
+	disabled by default, warns
 	  about performing class template argument deduction on a type with no
 	  deduction guides.
       </li>
-      <li><code>-Wrange-loop-construct</code>, enabled by <code>-Wall</code>,
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wrange-loop-construct"><code>-Wrange-loop-construct</code></a>,
+	enabled by <code>-Wall</code>,
 	  warns when a range-based for-loop is creating unnecessary and
 	  expensive copies.
       </li>
-      <li><code>-Wdeprecated-enum-enum-conversion</code>, enabled by default in
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-enum-conversion"><code>-Wdeprecated-enum-enum-conversion</code></a>,
+	enabled by default in
 	  C++20, warns about deprecated arithmetic conversions on operands of
 	  enumeration types, as outlined in <em>[depr.arith.conv.enum]</em>.
       </li>
-      <li><code>-Wdeprecated-enum-float-conversion</code>, enabled by default in
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wdeprecated-enum-float-conversion"><code>-Wdeprecated-enum-float-conversion</code></a>,
+	enabled by default in
 	  C++20, warns about deprecated arithmetic conversions on operands where
 	  one is of enumeration type and the other is of a floating-point type,
 	  as outlined in <em>[depr.arith.conv.enum]</em>.
@@ -399,7 +406,8 @@ a work-in-progress.</p>
 	forms of <code>operator new</code> or from other mismatched allocation
 	functions.
       </li>
-      <li><code>-Wvexing-parse</code>, enabled by default, warns about the most
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wvexing-parse"><code>-Wvexing-parse</code></a>,
+	enabled by default, warns about the most
 	  vexing parse rule: the cases when a declaration looks like a variable
 	  definition, but the C++ language requires it to be interpreted as a
 	  function declaration.

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-11/changes.html | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-02-10  0:45 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=20210210004524.AD1963858D29@sourceware.org \
    --to=msebor@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: link
Be 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).