public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 92327b22968879976973b2454b4db5cad1bddf52 Date: Fri, 6 Nov 2020 15:52:15 +0000 (GMT) [thread overview] Message-ID: <20201106155215.378EE3857806@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 92327b22968879976973b2454b4db5cad1bddf52 (commit) from 6ffde10eba0811d1223eaba7e2a8daefe26276aa (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 92327b22968879976973b2454b4db5cad1bddf52 Author: Marek Polacek <polacek@redhat.com> Date: Fri Nov 6 10:52:01 2020 -0500 gcc-11/changes: Document C++ -Wvexing-parse. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index dfa617a1..a124bfc9 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -202,6 +202,11 @@ a work-in-progress.</p> one is of enumeration type and the other is of a floating-point type, as outlined in <em>[depr.arith.conv.enum]</em>. </li> + <li><code>-Wvexing-parse</code>, 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. + </li> </ul> </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-11-06 15:52 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=20201106155215.378EE3857806@sourceware.org \ --to=mpolacek@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).