From: Jonathan Wakely <jwakely@redhat.com>
To: Thomas Rodgers <trodgers@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: libstdc++: Minor codegen improvement for atomic wait spinloop
Date: Thu, 7 Jul 2022 10:30:46 +0100 [thread overview]
Message-ID: <CACb0b4=gY2q7xobe2=jYjXG=eaLusSaXf4DfqV+vHmeFU_poDA@mail.gmail.com> (raw)
In-Reply-To: <CAMmuTO_dQAwbEDZNfou4eRvc3Vs4G8=616GH7gst98TarL+-9Q@mail.gmail.com>
On Wed, 6 Jul 2022 at 22:42, Thomas Rodgers <trodgers@redhat.com> wrote:
>
> Ok for trunk? backport?
Yes, for all branches that have the atomic wait code.
>
> On Wed, Jul 6, 2022 at 1:56 PM Jonathan Wakely <jwakely@redhat.com> wrote:
>>
>> On Wed, 6 Jul 2022 at 02:05, Thomas Rodgers via Libstdc++
>> <libstdc++@gcc.gnu.org> wrote:
>> >
>> > This patch merges the spin loops in the atomic wait implementation which is
>> > a
>> > minor codegen improvement.
>> >
>> > libstdc++-v3/ChangeLog:
>> > * include/bits/atomic_wait.h (__atomic_spin): Merge spin loops.
>>
>> OK, thanks.
>>
next prev parent reply other threads:[~2022-07-07 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 1:04 Thomas Rodgers
2022-07-06 20:56 ` Jonathan Wakely
2022-07-06 21:41 ` Thomas Rodgers
2022-07-07 9:30 ` Jonathan Wakely [this message]
2022-07-26 22:42 ` Thomas Rodgers
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='CACb0b4=gY2q7xobe2=jYjXG=eaLusSaXf4DfqV+vHmeFU_poDA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=trodgers@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).