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. d1abca5195cfd15aad393ae35fe899f53a86ebb2 Date: Thu, 11 May 2023 12:53:53 +0000 (GMT) [thread overview] Message-ID: <20230511125353.4733B3858C5F@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 d1abca5195cfd15aad393ae35fe899f53a86ebb2 (commit) via a09e584729c3136719d8870ad0c26870de8a552f (commit) from e0bfd617507326a26b301eeee207ca3a16c91ae5 (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 d1abca5195cfd15aad393ae35fe899f53a86ebb2 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Apr 28 13:47:12 2023 +0100 Add caveat about C++ iostream init changes (PR108969) Co-authored-by: Andrew Pinski <apinski@marvell.com> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 3d4870bd..bd022ed2 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -56,6 +56,18 @@ You may also want to check out our <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/ARM-iWMMXt-Built-in-Functions.html"> iWMMXt built-in functions</a>. </li> + <li>For C++, construction of the global iostream objects + <code>std::cout</code>, <code>std::cin</code>, etc. is now done + inside the standard library, instead of in every source file that + includes the <code><iostream></code> header. This change + improves the start-up performance of C++ programs, but it means that + code compiled with GCC 13.1 will crash if the correct version of + <code>libstdc++.so</code> is not used at runtime. See the + <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html#manual.intro.using.linkage.dynamic">documentation</a> + about using the right <code>libstdc++.so</code> at runtime. + Future GCC releases will mitigate the problem so that the program + cannot be run at all with an older <code>libstdc++.so</code>. + </li> </ul> commit a09e584729c3136719d8870ad0c26870de8a552f Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Mar 22 10:36:37 2023 +0000 Clarify experimental status of C++17 prior to GCC 9 Also link to library docs for C++20 and add a cxx2a anchor which is used by some old links. diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html index b5362bba..7f59e5a2 100644 --- a/htdocs/projects/cxx-status.html +++ b/htdocs/projects/cxx-status.html @@ -402,10 +402,12 @@ --> </table> - <h2 id="cxx20">C++20 Support in GCC</h2> + <h2 id="cxx20"><a id="cxx2a">C++20 Support in GCC</h2> <p>GCC has experimental support for the latest revision of the C++ - standard, which was published in 2020.</p> + standard, which was published in 2020. + The status of C++20 library features is described in + <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2020">the library documentation</a>.</p> <p>C++20 features are available since GCC 8. To enable C++20 support, add the command-line parameter <code>-std=c++20</code> @@ -988,14 +990,16 @@ <p>GCC has almost full support for the previous revision of the C++ standard, which was published in 2017. - Some library features are missing or incomplete, as described in + The status of C++17 library features is described in <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2017">the library documentation</a>. </p> - <p>C++17 features are available since GCC 5. This mode is the default - in GCC 11; it can be explicitly selected with the <code>-std=c++17</code> - command-line flag, or <code>-std=gnu++17</code> to enable GNU extensions - as well.</p> + <p>C++17 mode is the default since GCC 11; it can be explicitly selected + with the <code>-std=c++17</code> command-line flag, or + <code>-std=gnu++17</code> to enable GNU extensions as well. + Some C++17 features are available since GCC 5, but support was experimental + and the ABI of C++17 features was not stable until GCC 9. + </p> <h2>C++17 Language Features</h2> @@ -1315,7 +1319,7 @@ <p>GCC has full support for the of the 2014 C++ standard.</p> - <p>This mode is the default in GCC 6.1 up until GCC 10 (including); it can + <p>This mode is the default in GCC 6.1 up until GCC 10 (inclusive); it can be explicitly selected with the <code>-std=c++14</code> command-line flag, or <code>-std=gnu++14</code> to enable GNU extensions as well.</p> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 12 ++++++++++++ htdocs/projects/cxx-status.html | 20 ++++++++++++-------- 2 files changed, 24 insertions(+), 8 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-05-11 12:53 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=20230511125353.4733B3858C5F@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: linkBe 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).