public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 5c7b1c9688235e395b9f3583cbb91c82ca3d7486
Date: Wed, 15 Nov 2023 11:28:19 +0000 (GMT) [thread overview]
Message-ID: <20231115112819.83FDB3858D35@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 5c7b1c9688235e395b9f3583cbb91c82ca3d7486 (commit)
from ad756d3cfed3007d8c07c7f22facf24b202f1160 (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 5c7b1c9688235e395b9f3583cbb91c82ca3d7486
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Nov 15 12:28:14 2023 +0100
Adjust P1854R4 and P2361R6 C++26 status, add P2864R2 status
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 17e17a1c..3d3a7831 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -71,13 +71,13 @@
<tr>
<td> Making non-encodable string literals ill-formed </td>
<td><a href="https://wg21.link/P1854R4">P1854R4 </a> (<a href="./cxx-dr-status.html">DR</a>) </td>
- <td class="unsupported"> <a href="https://gcc.gnu.org/PR110341">No</a></td>
+ <td class="supported"> <a href="../gcc-14/changes.html#cxx">14</a></td>
<td> </td>
</tr>
<tr>
<td> Unevaluated strings </td>
<td> <a href="https://wg21.link/P2361R6">P2361R6</a></td>
- <td class="unsupported"> <a href="https://gcc.gnu.org/PR110342">No</a></td>
+ <td class="supported"> <a href="./gcc-14/changes.html#cxx">14</a></td>
<td> </td>
</tr>
<tr>
@@ -116,6 +116,13 @@
<td class="unsupported"> <a href="https://gcc.gnu.org/PR110349">No</a></td>
<td> __cpp_placeholder_variables >= 202306L </td>
</tr>
+ <!-- Fall 2023 papers (Kona) -->
+ <tr>
+ <td> Removing deprecated arithmetic conversion on enumerations </td>
+ <td><a href="https://wg21.link/P2864R2">P2864R2</a> (<a href="./cxx-dr-status.html">DR</a>) </td>
+ <td class="supported"> <a href="../gcc-14/changes.html#cxx">14</a></td>
+ <td> </td>
+ </tr>
<!--
<tr>
<td> </td>
-----------------------------------------------------------------------
Summary of changes:
htdocs/projects/cxx-status.html | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2023-11-15 11:28 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=20231115112819.83FDB3858D35@sourceware.org \
--to=jakub@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).