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. c0e26b54773236fee642d530969952e2f4998153 Date: Wed, 21 Sep 2022 09:31:43 +0000 (GMT) [thread overview] Message-ID: <20220921093143.A23043858CDB@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 c0e26b54773236fee642d530969952e2f4998153 (commit) via a962fbb84d1a05af682f35f5b6dad7e3371db308 (commit) from 60490c6e19f9d854721f271964c0379254aac244 (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 c0e26b54773236fee642d530969952e2f4998153 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Sep 21 10:17:02 2022 +0100 Add C++23 library additions to GCC 13 release notes diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 390193ca..a7d88038 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -158,7 +158,22 @@ a work-in-progress.</p> warnings have been extended to warn in more contexts.</li> </ul> -<!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> --> +<h4 id="libstdcxx">Runtime Library (libstdc++)</h4> +<ul> + <li>Improved experimental support for C++23, including: + <ul> + <li>Additions to the <code><ranges></code> header: + <code>views::zip</code>, <code>views::zip_transform</code>, + <code>views::adjacent</code>, <code>views::adjacent_transform</code> + <code>views::pairwise</code>, <code>views::slide</code>, + <code>views::chunk</code>, <code>views::chunk_by</code>. + </li> + </ul> + </li> + <li>Support for the <code><experimental/scope></code> header + from v3 of the Library Fundamentals Technical Specification. + </li> +</ul> <!-- <h3 id="d">D</h3> --> commit a962fbb84d1a05af682f35f5b6dad7e3371db308 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Sep 21 09:34:57 2022 +0100 Adjust "An Introduction to GCC" link to the actual book I meant to link to the HTML pages, not the promotional page for the printed version and PDF. diff --git a/htdocs/readings.html b/htdocs/readings.html index 5d1b78e8..3abdd2c4 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -22,7 +22,7 @@ <ul> - <li><a href="https://web.archive.org/web/20060106062936/http://www.network-theory.co.uk/gcc/intro/">An Introduction + <li><a href="https://web.archive.org/web/20060106062936/http://www.network-theory.co.uk/docs/gccintro/">An Introduction to GCC</a> by Brian J. Gough (<a href="https://archive.org/details/B-001-002-835/">e-book</a>).</li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 17 ++++++++++++++++- htdocs/readings.html | 2 +- 2 files changed, 17 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-09-21 9:31 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=20220921093143.A23043858CDB@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).