public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: gcc-wwwdocs branch master updated. f55f35c86c68143a2b148c66e4b0b560c852ce6f
Date: Tue, 24 May 2022 12:07:53 +0000 (GMT)	[thread overview]
Message-ID: <> (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  f55f35c86c68143a2b148c66e4b0b560c852ce6f (commit)
      from  b89dff3305518093bc2cbfce6f5bb4845992b88b (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 f55f35c86c68143a2b148c66e4b0b560c852ce6f
Author: Jonathan Wakely <>
Date:   Tue May 24 13:06:11 2022 +0100

    Document <cstdint> changes in libstdc++

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index b3e0895a..84a00f21 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -24,5 +24,23 @@ porting to GCC 13. This document is an effort to identify common issues
 and provide solutions. Let us know if you have suggestions for improvements!
+<h2 id="cxx">C++ language issues</h2>
+<h3 id="header-dep-changes">Header dependency changes</h3>
+<p>Some C++ Standard Library headers have been changed to no longer include
+other headers that were being used internally by the library.
+As such, C++ programs that used standard library components without
+including the right headers will no longer compile.
+The following headers are used less widely in libstdc++ and may need to
+be included explicitly when compiled with GCC 13:
+<li> <code>&lt;cstdint&gt;</code>
+  (for <code>std::int8_t</code>, <code>std::int32_t</code> etc.)


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


                 reply	other threads:[~2022-05-24 12:07 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).