public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Document <cstdint> changes in libstdc++
Date: Tue, 24 May 2022 13:08:26 +0100	[thread overview]
Message-ID: <YozKukuNCcIiJZD5@redhat.com> (raw)

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

Pushed to wwwdocs.

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

commit f55f35c86c68143a2b148c66e4b0b560c852ce6f
Author: Jonathan Wakely <jwakely@redhat.com>
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!
 </p>
 
+<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.
+</p>
+<p>
+The following headers are used less widely in libstdc++ and may need to
+be included explicitly when compiled with GCC 13:
+</p>
+<ul>
+<li> <code>&lt;cstdint&gt;</code>
+  (for <code>std::int8_t</code>, <code>std::int32_t</code> etc.)
+</li>
+</ul>
+
 </body>
 </html>

                 reply	other threads:[~2022-05-24 12:08 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=YozKukuNCcIiJZD5@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@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).