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-9979] Daily bump. Date: Wed, 15 Nov 2023 00:19:13 +0000 (GMT) [thread overview] Message-ID: <20231115001914.C64B83858D32@sourceware.org> (raw) https://gcc.gnu.org/g:7d0f1c7b6175daf6296bc6098ce23df065f5fd61 commit r12-9979-g7d0f1c7b6175daf6296bc6098ce23df065f5fd61 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Nov 15 00:18:49 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 d08907ad1a7..697a5fceddd 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20231114 +20231115 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 83dc1c3fcc1..6fd15099c9f 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,23 @@ +2023-11-14 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2023-11-14 Jonathan Wakely <jwakely@redhat.com> + + PR libstdc++/112348 + * include/std/stacktrace (hash<basic_stacktrace<Alloc>>): Fix + type of hash function for entries. + * testsuite/19_diagnostics/stacktrace/hash.cc: New test. + +2023-11-14 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2023-11-14 Jonathan Wakely <jwakely@redhat.com> + + PR libstdc++/112491 + * python/libstdcxx/v6/xmethods.py (DequeWorkerBase.size): Fix + calculation to use _M_start._M_cur. + * testsuite/libstdc++-xmethods/deque.cc: Check failing cases. + 2023-11-13 Tom Tromey <tromey@adacore.com> Backported from master:
reply other threads:[~2023-11-15 0:19 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=20231115001914.C64B83858D32@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: 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).