public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: gcc-wwwdocs branch master updated. 6ffde10eba0811d1223eaba7e2a8daefe26276aa
Date: Wed,  4 Nov 2020 12:58:58 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]

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  6ffde10eba0811d1223eaba7e2a8daefe26276aa (commit)
      from  561b07983ed3bfaec2d9f19922f5e70526a86bf5 (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 6ffde10eba0811d1223eaba7e2a8daefe26276aa
Author: Jonathan Wakely <>
Date:   Wed Nov 4 12:58:19 2020 +0000

    Document std::istreambuf_iterator change in GCC 10 [PR 92285]

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 759e4fd7..d40a633c 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -65,6 +65,12 @@ You may also want to check out our
     Language (HSAIL) has been deprecated and will likely be removed in
     a future release.
+  <li>
+    The type of the <code>std::iterator</code> base class of
+    <code>std::istreambuf_iterator</code> was changed in C++98 mode
+    to be consistent with C++11 and later standards.
+    See the <a href="#iterator_base">libstdc++ notes below</a> for more details.
+  </li>
@@ -504,6 +510,18 @@ int get_naïve_pi() {
     Reduced header dependencies, leading to faster compilation for some code.
+  <li>
+    <a id="iterator_base">The <code>std::iterator</code></a> base class of
+    <code>std::istreambuf_iterator</code> was changed in C++98 mode
+    to be consistent with C++11 and later standards.
+    This is expected to have no noticeable effect except in the unlikely case
+    of a class which has potentially overlapping subobjects of type
+    <code>std::istreambuf_iterator&lt;C&gt;</code> and another iterator type
+    with a <code>std::iterator&lt;input_iterator_tag, C, ...&gt;</code>
+    base class. The layout of such a type might change when compiled as C++98.
+    <a href="">Bug 92285</a>
+    has more details and concrete examples.
+  </li>
 <h3 id="d">D</h3>


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


                 reply	other threads:[~2020-11-04 12:58 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).