public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org
Subject: [wwwdocs] Document libstdc++ changes in GCC 11
Date: Tue, 8 Dec 2020 13:07:38 +0000	[thread overview]
Message-ID: <20201208130738.GA4193258@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 65 bytes --]

Also add porting-to notes about tr1::bind.

Pushed to wwwdocs.



[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 3032 bytes --]

commit 927e80dc01f505a625f1fcc4e1ca38aeb9f88e67
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Dec 8 13:05:42 2020 +0000

    Document libstdc++ changes in GCC 11
    
    Also add porting-to notes about tr1::bind.

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 4d3efed5..50e35505 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -239,7 +239,28 @@ a work-in-progress.</p>
   </li>
 </ul>
 
-<!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> -->
+<h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
+<ul>
+  <li>Improved C++17 support, including:
+    <ul>
+      <li><code>std::from_chars</code> for floating-point types.
+    <ul>
+  </li>
+  <li>Improved experimental C++2a support, including:
+    <ul>
+      <li>Calendar additions to <code>&lt;chrono&gt;</code>.</li>
+      <li><code>std::bit_cast</code></li>
+      <li><code>std::source_location</code></li>
+      <li>Atomic wait and notify operations.</li>
+      <li><code>&lt;latch&gt;</code> and <code>&lt;semaphore&gt;</code></li>
+      <li><code>&lt;syncstream&gt;</code></li>
+      <li>Efficient access to <code>basic_stringbuf</code>'s buffer.</li>
+    </ul>
+  </li>
+  <li>Faster <code>std::uniform_int_distribution</code>,
+      thanks to Daniel Lemire.
+  </li>
+</ul>
 
 <h3 id="fortran">Fortran</h3>
 
diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html
index 41efc3b6..4187dd8e 100644
--- a/htdocs/gcc-11/porting_to.html
+++ b/htdocs/gcc-11/porting_to.html
@@ -114,6 +114,33 @@ be included explicitly when compiled with GCC 11:
 </li>
 </ul>
 
+<h3 id="Old-iostream-Members">Old iostream Members</h3>
+<p>
+The deprecated iostream members <code>ios_base::io_state</code>,
+<code>ios_base::open_mode</code>, <code>ios_base::seek_dir</code>, and
+<code>basic_streambuf::stossc</code> are not available in C++17 mode.
+References to those members should be replaced by <code>std::iostate</code>,
+<code>std::openmode</code>, <code>std::seekdir</code>, and
+<code>basic_streambuf::sbumpc</code> respectively.
+</p>
+
+<h3 id="tr1-bind">Call of overloaded <code>'bind(...)'</code> is ambiguous</h3>
+<p>
+The placeholders for <code>std::tr1::bind</code> have been changed to use
+the same placeholder objects as <code>std::bind</code>.  This means that
+following <code>using std::tr1::bind;</code> an unqualified call to
+<code>bind(f, std::tr1::placeholders::_1)</code> may be ambiguous.
+This happens because <code>std::tr1::bind</code> is brought into scope by
+the using-declaration and <code>std::bind</code> is found by
+Argument-Dependent Lookup due to the type of the <code>_1</code> placeholder.
+</p>
+<p>
+To resolve this ambiguity replace unqualified calls to <code>bind</code>
+with <code>std::tr1::bind</code> or <code>std::bind</code>. Alternatively,
+change the code to not include the <code>&lt;tr1/functional&gt;</code> header,
+so that only <code>std::bind</code> is declared.
+</p>
+
 <!--
 <h2 id="fortran">Fortran language issues</h2>
 -->

             reply	other threads:[~2020-12-08 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 13:07 Jonathan Wakely [this message]
2020-12-08 13:18 ` Jonathan Wakely

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=20201208130738.GA4193258@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).