public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r12-10030] Daily bump.
Date: Thu, 7 Dec 2023 00:20:08 +0000 (GMT) [thread overview]
Message-ID: <20231207002008.48A8C3858C2A@sourceware.org> (raw)
https://gcc.gnu.org/g:a1518c7b34c8010d74af84fa3dd0b19e4471f649
commit r12-10030-ga1518c7b34c8010d74af84fa3dd0b19e4471f649
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Thu Dec 7 00:19:43 2023 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
libstdc++-v3/ChangeLog | 20 ++++++++++++++++++++
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 76ff872532c..af1f8a0d719 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20231206
+20231207
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index fea3725c8ff..efd12aa82f3 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,23 @@
+2023-12-06 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2023-11-02 Jonathan Wakely <jwakely@redhat.com>
+
+ PR libstdc++/112314
+ * include/std/string_view (string_view::remove_suffix): Add
+ debug assertion.
+ * testsuite/21_strings/basic_string_view/modifiers/remove_prefix/debug.cc:
+ New test.
+ * testsuite/21_strings/basic_string_view/modifiers/remove_suffix/debug.cc:
+ New test.
+
+2023-12-06 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2023-11-17 Jonathan Wakely <jwakely@redhat.com>
+
+ * include/std/utility (in_range): Rename _Up parameter to _Res.
+
2023-11-15 Jonathan Wakely <jwakely@redhat.com>
Backported from master:
reply other threads:[~2023-12-07 0:20 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=20231207002008.48A8C3858C2A@sourceware.org \
--to=gccadmin@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-cvs@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).