public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: gcc-wwwdocs branch master updated. e870a90578545e04dea26cd9d9aa32dff2212834
Date: Fri, 25 Mar 2022 13:26:10 +0000 (GMT)	[thread overview]
Message-ID: <> (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  e870a90578545e04dea26cd9d9aa32dff2212834 (commit)
      from  026ac01f467563e529964c97ca5fec11c348540e (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 e870a90578545e04dea26cd9d9aa32dff2212834
Author: Jonathan Wakely <>
Date:   Fri Mar 25 13:25:33 2022 +0000

    Add functions that require <iterator> to GCC 12 porting-to docs

diff --git a/htdocs/gcc-12/porting_to.html b/htdocs/gcc-12/porting_to.html
index 470703c7..079bda30 100644
--- a/htdocs/gcc-12/porting_to.html
+++ b/htdocs/gcc-12/porting_to.html
@@ -67,7 +67,8 @@ be included explicitly when compiled with GCC 12:
   (for <code>std::shared_ptr</code>, <code>std::unique_ptr</code> etc.)
 <li> <code>&lt;iterator&gt;</code>
-  (for <code>std::istream_iterator</code>, <code>std::istreambuf_iterator</code>)
+  (for <code>std::begin</code>, <code>std::end</code>, <code>std::size</code>,
+  <code>std::istream_iterator</code>, <code>std::istreambuf_iterator</code>)
 <li> <code>&lt;algorithm&gt;</code>
   (for <code>std::for_each</code>, <code>std::copy</code> etc.)


Summary of changes:
 htdocs/gcc-12/porting_to.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)


                 reply	other threads:[~2022-03-25 13:26 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).