public inbox for gcc-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 r11-10473] Daily bump. Date: Thu, 19 Jan 2023 00:20:44 +0000 (GMT) [thread overview] Message-ID: <20230119002045.2971B3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:5f30fae901cc442829350677519e534d41e758e9 commit r11-10473-g5f30fae901cc442829350677519e534d41e758e9 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Thu Jan 19 00:20:03 2023 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 14 ++++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 5943f2b395d..847dee113d4 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230118 +20230119 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index a7aa638dc05..893662c74dc 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,17 @@ +2023-01-18 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2022-08-04 Jonathan Wakely <jwakely@redhat.com> + + PR libstdc++/106183 + * include/bits/atomic_wait.h (__waiter_pool_base::_M_notify): + Move increment of _M_ver here. + [!_GLIBCXX_HAVE_PLATFORM_WAIT]: Lock mutex around increment. + Use relaxed memory order and always notify all waiters. + (__waiter_base::_M_do_wait) [!_GLIBCXX_HAVE_PLATFORM_WAIT]: + Check value again after locking mutex. + (__waiter_base::_M_notify): Remove increment of _M_ver. + 2022-12-22 Jonathan Wakely <jwakely@redhat.com> Backported from master:
reply other threads:[~2023-01-19 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=20230119002045.2971B3858D28@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).