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. 1fc7bcff402ffd58300db5bec6c2644744c4cee8 Date: Fri, 3 Jul 2020 18:33:18 +0000 (GMT) [thread overview] Message-ID: <20200703183318.1C8293844079@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 1fc7bcff402ffd58300db5bec6c2644744c4cee8 (commit) from c325a1addc0fc612a9db218be6abb41b2052a447 (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 1fc7bcff402ffd58300db5bec6c2644744c4cee8 Author: Marek Polacek <polacek@redhat.com> Date: Fri Jul 3 14:33:02 2020 -0400 gcc-11/changes: Another C++ improvement. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 287dc864..b9ca04bb 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -91,6 +91,8 @@ a work-in-progress.</p> </li> <li>G++ now performs better access checking in templates (<a href="https://gcc.gnu.org/PR41437">PR41437</a>).</li> + <li><code>reinterpreter_cast</code>s in constexpr evaluation are now checked + more completely (<a href="https://gcc.gnu.org/PR95307">PR95307</a>).</li> </ul> <!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-07-03 18:33 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=20200703183318.1C8293844079@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).