From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: C++ patch ping^2
Date: Tue, 10 Oct 2023 15:56:36 +0200 [thread overview]
Message-ID: <ZSVYFIewz18LmkTa@tucnak> (raw)
Hi!
I'd like to ping a couple of C++ patches.
- c++, v2: Implement C++26 P2169R4 - Placeholder variables with no name [PR110349]
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630802.html
- c++: Implement C++26 P2361R6 - Unevaluated strings [PR110342]
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628375.html
- c++, v2: Implement C++26 P2741R3 - user-generated static_assert messages [PR110348]
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630803.html
- c++: Implement C++ DR 2406 - [[fallthrough]] attribute and iteration statements [PR107571]
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628487.html
(from this one Richi approved the middle-end changes)
- c++: Implement C++26 P1854R4 - Making non-encodable string literals ill-formed [PR110341]
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628490.html
- libcpp, v2: Small incremental patch for P1854R4 [PR110341]
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628586.html
Jakub
next reply other threads:[~2023-10-10 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 13:56 Jakub Jelinek [this message]
2023-11-13 11:58 ` C++ patch ping^3 Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 9:48 C++ Patch ping Jakub Jelinek
2024-04-10 11:02 ` C++ Patch ping^2 Jakub Jelinek
2020-11-18 9:38 C++ patch ping^2 Jakub Jelinek
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=ZSVYFIewz18LmkTa@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).