Sujet : Re: Atomic caching of smart pointers
De : news.5.maazl (at) *nospam* spamgourmet.org (Marcel Mueller)
Groupes : comp.lang.c++Date : 16. Sep 2024, 17:23:26
Autres entêtes
Organisation : MB-NET.NET for Open-News-Network e.V.
Message-ID : <vc9m1u$g3eq$2@gwaiyur.mb-net.net>
References : 1 2 3
User-Agent : Mozilla Thunderbird
Am 16.09.24 um 08:01 schrieb Paavo Helde:
Meanwhile I think I found a bug in my posted code, I should probably use compare_exchange_strong() instead of compare_exchange_weak().
Indeed. With ..._weak you most likely need a loop. But if you already have a loop for other purposes using the _weak function could avoid an additional loop in the implementation of the function.
I somehow thought the latter would err on the safe side, but it does not. In my test harness there seems to be no difference.
On many platforms the underlying CAS primitives already are strong. In this cases both function are identical.
Marcel
Atomic caching of smart pointers
Re: Atomic caching of smart pointers