public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 62250c79a7483076f1b2b11496e4a1123c9df6a0
Date: Thu, 11 Jan 2024 12:48:09 +0000 (GMT)	[thread overview]
Message-ID: <20240111124809.E3FB6384DED4@sourceware.org> (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  62250c79a7483076f1b2b11496e4a1123c9df6a0 (commit)
       via  d519c7ed720ebdf07bd2af45286d4fbed0632a33 (commit)
      from  b4fd94ebe3f1b50a1d83d0c3cfdad37fd467d44c (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 62250c79a7483076f1b2b11496e4a1123c9df6a0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 11 12:47:40 2024 +0000

    Document additional symbols in libstdc++exp.a for GCC 13.3

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index b4b1a39a..6930bd58 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -858,6 +858,32 @@ known to be fixed in the 13.2 release. This list might not be
 complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
+<!-- .................................................................. -->
+<h2 id="13.3">GCC 13.3</h2>
+
+<p>Note: GCC 13.3 has not been released yet, so this section is a
+work-in-progress.</p>
+
+<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;resolution=FIXED&amp;target_milestone=13.3">list
+of problem reports (PRs)</a> from GCC's bug tracking system that are
+known to be fixed in the 13.3 release. This list might not be
+complete (that is, it is possible that some PRs that have been fixed
+are not listed here).</p>
+
+<h3>Language Specific Changes</h3>
+
+<h3>C++</h3>
+<ul>
+  <li>
+    The <code>libstdc++exp.a</code> library now includes all the Filesystem TS
+    symbols from the <code>libstdc++fs.a</code> library,
+    and the experimental symbols for the C++23 <code>std::stacktrace</code>
+    class from the <code>libstdc++_libbacktrace.a</code> library.
+    This means that <code>-lstdc++exp</code> is the only library needed for
+    all experimental libstdc++ features.
+  </li>
+</ul>
+
 <!-- .................................................................. -->
 
 </body>

commit d519c7ed720ebdf07bd2af45286d4fbed0632a33
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Sat Dec 16 22:55:29 2023 +0000

    Update notes on libstdc++ header dependency changes in GCC 14

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index dea9ac80..3e4cedc3 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -38,10 +38,14 @@ be included explicitly when compiling with GCC 14:
 </p>
 <ul>
 <li> <code>&lt;algorithm&gt;</code>
-  (for <code>std::copy_n</code>, <code>std::lower_bound</code>,
+  (for <code>std::copy_n</code>, <code>std::find_if</code>,
+  <code>std::lower_bound</code>,
   <code>std::remove</code>, <code>std::reverse</code>,
   <code>std::sort</code> etc.)
 </li>
+<li> <code>&lt;cstdint&gt;</code>
+  (for <code>std::int8_t</code>, <code>std::int32_t</code> etc.)
+</li>
 </ul>
 
 <!-- <h2 id="fortran">Fortran language issues</h2> -->

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html    | 26 ++++++++++++++++++++++++++
 htdocs/gcc-14/porting_to.html |  6 +++++-
 2 files changed, 31 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-01-11 12:48 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=20240111124809.E3FB6384DED4@sourceware.org \
    --to=redi@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).