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. ddc57d349aa96e7942fee94eb21c7c0f4b65766e Date: Mon, 20 Jul 2020 22:57:57 +0000 (GMT) [thread overview] Message-ID: <20200720225757.DA7E33857C79@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 ddc57d349aa96e7942fee94eb21c7c0f4b65766e (commit) from 1f9ebcc8f95b1e07b96b20eab377fb4cd418e936 (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 ddc57d349aa96e7942fee94eb21c7c0f4b65766e Author: Marek Polacek <polacek@redhat.com> Date: Mon Jul 20 18:57:50 2020 -0400 gcc-11/changes:: Document new C++ stuff. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index b9ca04bb..d3fb9882 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -80,6 +80,9 @@ a work-in-progress.</p> <ul> <li>the compiler now supports <code>consteval virtual</code> functions</li> <li>P2082R1, Fixing CTAD for aggregates</li> + <li>P0593R6, Pseudo-destructors end object lifetimes</li> + <li>P1907R1: Inconsistencies with non-type template parameters (complete + implementation)</li> </ul> </li> <li>Several C++ Defect Reports have been resolved, e.g.: ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-07-20 22:57 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=20200720225757.DA7E33857C79@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).