From: Thomas Rodgers <trodgers@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Fix deadlock in atomic wait [PR104442]
Date: Wed, 9 Feb 2022 12:33:44 -0800 [thread overview]
Message-ID: <CAMmuTO-Dks2TNn5QQ=TLeAej3P9ML9H=O-38GErCfdw6djEzQA@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4mMYx9-oQ3q+FfMMpWgh+gJ3UX0C6B7CmKVBMqfYqQUdw@mail.gmail.com>
Tested x86_64-pc-linux-gnu, committed to master, backported to gcc-11.
On Wed, Feb 9, 2022 at 9:14 AM Jonathan Wakely <jwakely@redhat.com> wrote:
> On Wed, 9 Feb 2022 at 17:10, Thomas Rodgers wrote:
> >
> > Updated patch. I reverted the memory order change (and will submit that
> as another patch) and fixed some spelling and grammar errors.
>
> OK for trunk and gcc-11, thanks.
>
>
prev parent reply other threads:[~2022-02-09 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 0:55 Thomas Rodgers
2022-02-09 10:42 ` Jonathan Wakely
2022-02-09 15:13 ` Thomas Rodgers
2022-02-09 17:10 ` Thomas Rodgers
2022-02-09 17:13 ` Jonathan Wakely
2022-02-09 20:33 ` Thomas Rodgers [this message]
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='CAMmuTO-Dks2TNn5QQ=TLeAej3P9ML9H=O-38GErCfdw6djEzQA@mail.gmail.com' \
--to=trodgers@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).