From: Thomas Rodgers <rodgert@appliantology.com>
To: Mikhail Matrosov <mikhail.matrosov@gmail.com>
Cc: libstdc++@gcc.gnu.org
Subject: Re: std::atomic_shared_ptr
Date: Tue, 01 Jun 2021 19:16:38 -0700 [thread overview]
Message-ID: <6e2006356de7157302748c8cf7a9dc48@appliantology.com> (raw)
In-Reply-To: <e4d8f6a49ba0a6338afb239a1e5028ef@appliantology.com>
On 2021-06-01 18:57, Thomas Rodgers wrote:
> On 2021-06-01 12:35, Mikhail Matrosov via Libstdc++ wrote:
>
>> Could anyone please share the status of the implementation
>> of std::atomic_shared_ptr?
>>
>> -----
>> Best regards, Mikhail Matrosov
>
> It didn't make the cutoff for GCC11 stage1, I hope to get it into
> GCC12.
Also, to set expectations, it will not be a lock free atomic.
next prev parent reply other threads:[~2021-06-02 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 19:35 std::atomic_shared_ptr Mikhail Matrosov
2021-06-02 1:57 ` std::atomic_shared_ptr Thomas Rodgers
2021-06-02 2:16 ` Thomas Rodgers [this message]
2021-06-02 7:10 ` std::atomic_shared_ptr Mikhail Matrosov
2021-06-02 9:22 ` std::atomic_shared_ptr Jonathan Wakely
2021-06-02 14:37 ` std::atomic_shared_ptr Mikhail Matrosov
2021-06-02 15:03 ` std::atomic_shared_ptr 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=6e2006356de7157302748c8cf7a9dc48@appliantology.com \
--to=rodgert@appliantology.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mikhail.matrosov@gmail.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).