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. 0ee90c1a9c4f131e37aedd6b232cbf1f3f042da4 Date: Wed, 26 Oct 2022 19:22:12 +0000 (GMT) [thread overview] Message-ID: <20221026192212.854A6385737A@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 0ee90c1a9c4f131e37aedd6b232cbf1f3f042da4 (commit) from 1c3fd72e73045266479669ff4a97a63520a0e72b (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 0ee90c1a9c4f131e37aedd6b232cbf1f3f042da4 Author: Marek Polacek <polacek@redhat.com> Date: Wed Oct 26 15:21:46 2022 -0400 gcc-13/changes: Mention -Wdangling-reference diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 033cc6a2..7c6bfa6e 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -167,6 +167,9 @@ a work-in-progress.</p> <li><code>-Wself-move</code> warns when a value is moved to itself with <code>std::move</code> (<a href="https://gcc.gnu.org/PR81159">PR81159</a>)</li> + <li><code>-Wdangling-reference</code> warns when a reference is bound to + a temporary whose lifetime has ended + (<a href="https://gcc.gnu.org/PR106393">PR106393</a>)</li> </ul> </li> <li>The <code>-Wpessimizing-move</code> and <code>-Wredundant-move</code> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-10-26 19:22 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=20221026192212.854A6385737A@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).