From: Jonathan Wakely <jwakely@redhat.com>
To: "Alessio G. B." <alessiogiovanni.baroni@gmail.com>
Cc: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Implementation of class strand
Date: Tue, 23 Mar 2021 16:39:37 +0000 [thread overview]
Message-ID: <20210323163937.GA3008@redhat.com> (raw)
In-Reply-To: <CANDuHT+S6jZyOohT9f+hhSOkj=0K9vnVhQUK5oV2HhFg2D=t5g@mail.gmail.com>
On 12/03/21 13:21 +0100, Alessio G. B. via Libstdc++ wrote:
>I expanded the implementation of the class strand of the Networking
>TS. Essentially, I
>implemented a token system so each thread knows when it can execute;
>the system is organized
>with 2 integers moving as a clock.
Thanks for this patch. I'm not sure when I'll have time to review it,
and it might not be in time for the upcoming GCC 11 release. But the
patch has been received and will get reviewed, thanks.
N.B. patches being submitted for libstdc++ should be CC'd to the
gcc-patches list (where all GCC patches get sent) as well as the
libstdc++ list.
next prev parent reply other threads:[~2021-03-23 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 12:21 Alessio G. B.
2021-03-23 16:39 ` Jonathan Wakely [this message]
2023-03-22 14:31 ` Jonathan Wakely
2023-04-10 19: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=20210323163937.GA3008@redhat.com \
--to=jwakely@redhat.com \
--cc=alessiogiovanni.baroni@gmail.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).