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. c47e7251a822a5068249ba6eb875a1fbd3fecc8b
Date: Thu, 11 May 2023 15:52:37 +0000 (GMT)	[thread overview]
Message-ID: <20230511155237.CACC93858C5F@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]

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  c47e7251a822a5068249ba6eb875a1fbd3fecc8b (commit)
      from  d1abca5195cfd15aad393ae35fe899f53a86ebb2 (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 c47e7251a822a5068249ba6eb875a1fbd3fecc8b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu May 11 14:06:31 2023 +0100

    Document libstdc++ freestanding changes in gcc-13

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index bd022ed2..39414e18 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -412,6 +412,20 @@ You may also want to check out our
   <li>Support for the <code>&lt;experimental/synchronized_value&gt;</code>
       header from v2 of the Concurrency Technical Specification.
   </li>
+  <li>Support for many previously unavailable features in freestanding mode,
+      thanks to Arsen Arsenović. For example, <code>std::tuple</code> is
+      now available for freestanding compilation. The freestanding subset
+      contains all the components made freestanding by
+      <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1642r11.html">P1642</a>,
+      but libstdc++ adds more components to the freestanding subset,
+      such as <code>std::array</code> and <code>std::string_view</code>.
+      Additionally, libstdc++ now respects the <code>-ffreestanding</code>
+      compiler option and so it is not necessary to build a separate
+      freestanding installation of libstdc++.  Compiling with
+      <code>-ffreestanding</code> will restrict the available features to
+      the freestanding subset, even if libstdc++ was built as a full, hosted
+      implementation.
+  </li>
 </ul>
 
 <!-- <h3 id="d">D</h3> -->

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-05-11 15:52 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=20230511155237.CACC93858C5F@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).