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. 693cc9122512b580926acacf2b7516b0a23b770a
Date: Tue, 29 Sep 2020 23:10:02 +0000 (GMT)	[thread overview]
Message-ID: <20200929231003.01B2C386F44F@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  693cc9122512b580926acacf2b7516b0a23b770a (commit)
      from  7eb81fbabc8ede30c1482f9452b1825d7fbd8c56 (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 693cc9122512b580926acacf2b7516b0a23b770a
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Sep 29 19:09:43 2020 -0400

    gcc-11/changes: Add -Wrange-loop-construct.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index ac71119d..64655120 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -132,6 +132,10 @@ a work-in-progress.</p>
 	  about performing class template argument deduction on a type with no
 	  deduction guides.
       </li>
+      <li><code>-Wrange-loop-construct</code>, enabled by <code>-Wall</code>,
+	  warns when a range-based for-loop is creating unnecessary and
+	  expensive copies.
+      </li>
     </ul>
   </li>
 </ul>

-----------------------------------------------------------------------

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-09-29 23:10 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=20200929231003.01B2C386F44F@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: 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).