From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [wwwdocs] Document std::istreambuf_iterator change in GCC 10 [PR 92285]
Date: Wed, 4 Nov 2020 13:00:44 +0000 [thread overview]
Message-ID: <20201104130044.GA3194479@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 110 bytes --]
I'm adding this caveat to the gcc-10 release notes, as well as to the
libstdc++ manual.
Pushed to wwwdocs.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1706 bytes --]
commit 6ffde10eba0811d1223eaba7e2a8daefe26276aa
Author: Jonathan Wakely <jwakely@redhat.com>
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>
+ <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>
</ul>
@@ -504,6 +510,18 @@ int get_naïve_pi() {
<li>
Reduced header dependencies, leading to faster compilation for some code.
</li>
+ <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<C></code> and another iterator type
+ with a <code>std::iterator<input_iterator_tag, C, ...></code>
+ base class. The layout of such a type might change when compiled as C++98.
+ <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92285">Bug 92285</a>
+ has more details and concrete examples.
+ </li>
</ul>
<h3 id="d">D</h3>
reply other threads:[~2020-11-04 13:01 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=20201104130044.GA3194479@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).