public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [wwwdocs] Document libstdc++ changes in GCC 14
Date: Mon, 18 Sep 2023 14:01:33 +0100	[thread overview]
Message-ID: <20230918130141.2460012-1-jwakely@redhat.com> (raw)

Pushed to wwwdocs.


---
 htdocs/gcc-14/changes.html | 48 +++++++++++++++++++++++++++++++++++++-
 1 file changed, 47 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index eae25f1a..65382746 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -97,7 +97,53 @@ a work-in-progress.</p>
   </li>
 </ul>
 
-<!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> -->
+<h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
+
+<ul>
+  <li>
+    The <code>libstdc++exp.a</code> library now includes all the Filesystem TS
+    symbols from the <code>libstdc++fs.a</code> library.
+    The experimental symbols for the C++23 <code>std::stacktrace</code> class
+    are also in <code>libstdc++exp.a</code>, replacing the
+    <code>libstdc++_libbacktrace.a</code> library that GCC 13 provides.
+    This means that <code>-lstdc++exp</code> is the only library needed for
+    all experimental libstdc++ features.
+  </li>
+  <li>Improved experimental support for C++20, including:
+    <ul>
+    <li><code>std::chrono::parse</code>.</li>
+    </ul>
+  </li>
+  <li>Improved experimental support for C++23, including:
+    <ul>
+    <li>The <code>&lt;stacktrace&gt;</code> header is supported by default.
+    </li>
+    <li>Formatters for <code>std::thread::id</code> and
+      <code>std::stacktrace</code>.
+    </li>
+    <li>Some range adaptors now support move-only types.</li>
+    </ul>
+  </li>
+  <li>Experimental support for C++26, including:
+    <ul>
+    <li>Native handles for <code>filebuf</code>, <code>fstream</code>, etc.</li>
+    <li><code>std::to_string</code> now uses <code>std::format</code>.</li>
+    <li>Enhanced formatting of pointers with <code>std::format</code>.</li>
+    <li>Testable result types for <code>&lt;charconv&gt;</code> functions.</li>
+    </ul>
+  </li>
+  <li>Faster numeric conversions using <code>std::to_string</code> and
+    <code>std::to_wstring</code>.
+  </li>
+  <li>Updated parallel algorithms that are compatible with oneTBB.</li>
+  <li><code>std::numeric_limits&lt;_Float32&gt;</code> and
+    <code>std::numeric_limits&lt;_Float64&gt;</code> are now defined
+    for all standard modes, not only for C++23.
+  </li>
+  <li>Using the <code>std::setfill</code> manipulator with
+    <code>std::istream</code> is deprecated.
+  </li>
+</ul>
 
 <!-- <h3 id="d">D</h3> -->
 
-- 
2.41.0


                 reply	other threads:[~2023-09-18 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=20230918130141.2460012-1-jwakely@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).