Date: Thu, 25 May 2023 15:43:49 -0400
Because either it wasn't available with GCC 9, _GLIBCXX_USE_CXX11_ABI=0
or the simple fact atomic operations still doesn't fix the defective
reset() call.
I can't remember exactly.
On 5/25/23 15:30, Jens Maurer wrote:
>
>
> On 25/05/2023 21.17, Phil Bouchard via Std-Proposals wrote:
>> 2nd round of clarifications:
>>
>> The exact problem was OpenCV which is not using thread-safe reference
>> count smart pointers has a race-condition. It turns out C++ doesn't even
>> offer thread-safe reference count pointers anyways.
>
> In which way does std::atomic<std::shared_ptr<T>>
> as specified in [util.smartptr.atomic.shared] not satisfy your requirements?
>
> Jens
or the simple fact atomic operations still doesn't fix the defective
reset() call.
I can't remember exactly.
On 5/25/23 15:30, Jens Maurer wrote:
>
>
> On 25/05/2023 21.17, Phil Bouchard via Std-Proposals wrote:
>> 2nd round of clarifications:
>>
>> The exact problem was OpenCV which is not using thread-safe reference
>> count smart pointers has a race-condition. It turns out C++ doesn't even
>> offer thread-safe reference count pointers anyways.
>
> In which way does std::atomic<std::shared_ptr<T>>
> as specified in [util.smartptr.atomic.shared] not satisfy your requirements?
>
> Jens
-- Logo <https://www.fornux.com/> *Phil Bouchard* facebook icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> Founder & CEO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les documents l'accompagnant, sont destinés uniquement aux personnes identifiées et peuvent contenir des informations privilégiées, confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce message par erreur, veuillez le détruire. This communication (and/or the attachments) is intended for named recipients only and may contain privileged or confidential information which is not to be disclosed. If you received this communication by mistake please destroy all copies.
Received on 2023-05-25 19:43:51