public inbox for
help / color / mirror / Atom feed
From: Marek Polacek <>
Subject: gcc-wwwdocs branch master updated. 3ecf83c60b4c021716bc6c981a7f9acdf8fd0261
Date: Tue, 10 Nov 2020 20:18:14 +0000 (GMT)	[thread overview]
Message-ID: <> (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  3ecf83c60b4c021716bc6c981a7f9acdf8fd0261 (commit)
      from  7dbbae5e3c469f89775eb104f0ad5bdb1a91fab9 (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 3ecf83c60b4c021716bc6c981a7f9acdf8fd0261
Author: Marek Polacek <>
Date:   Tue Nov 10 15:17:42 2020 -0500

    gcc-11/changes: Document C++ static_assert improvements.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 0fce64cd..d7a3a1f9 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -186,6 +186,11 @@ a work-in-progress.</p>
       (<a href="">PR41437</a>).</li>
   <li><code>reinterpret_cast</code>s in constexpr evaluation are now checked
       more completely (<a href="">PR95307</a>).</li>
+  <li>The diagnostic for <code>static_assert</code> has been improved: the
+      compiler now shows the expression including its template arguments (if
+      there were any), and can point to the failing clause if the condition
+      comprised of any logical AND operators
+      (<a href="">PR97518</a>).</li>
   <li>New warnings:
       <li><code>-Wctad-maybe-unsupported</code>, disabled by default, warns


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


                 reply	other threads:[~2020-11-10 20:18 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).