std::atomic_...<std::shared_ptr>
<memory>
bool atomic_is_lock_free( const std::shared_ptr <T>* p );
(deprecated in C++20)
(removed in C++26)
std::shared_ptr <T> atomic_load( const std::shared_ptr <T>* p );
(deprecated in C++20)
(removed in C++26)
std::shared_ptr <T> atomic_load_explicit
(deprecated in C++20)
(removed in C++26)
void atomic_store( std::shared_ptr <T>* p, std::shared_ptr <T> r );
(deprecated in C++20)
(removed in C++26)
void atomic_store_explicit
( std::shared_ptr <T>* p, std::shared_ptr <T> r,
(deprecated in C++20)
(removed in C++26)
std::shared_ptr <T> atomic_exchange
(deprecated in C++20)
(removed in C++26)
std::shared_ptr <T> atomic_exchange_explicit
( std::shared_ptr <T>* p, std::shared_ptr <T> r,
(deprecated in C++20)
(removed in C++26)
bool atomic_compare_exchange_weak
( std::shared_ptr <T>* p, std::shared_ptr <T>* expected,
(deprecated in C++20)
(removed in C++26)
bool atomic_compare_exchange_strong
( std::shared_ptr <T>* p, std::shared_ptr <T>* expected,
(deprecated in C++20)
(removed in C++26)
bool atomic_compare_exchange_strong_explicit
( std::shared_ptr <T>* p, std::shared_ptr <T>* expected,
std::shared_ptr <T> desired,
(deprecated in C++20)
(removed in C++26)
bool atomic_compare_exchange_weak_explicit
( std::shared_ptr <T>* p, std::shared_ptr <T>* expected,
std::shared_ptr <T> desired,
(deprecated in C++20)
(removed in C++26)
If multiple threads of execution access the same std::shared_ptr object without synchronization and any of those accesses uses a non-const member function of shared_ptr
then a data race will occur unless all such access is performed through these functions, which are overloads of the corresponding atomic access functions (std::atomic_load , std::atomic_store , etc.).
Note that the control block of a shared_ptr
is thread-safe: different std::shared_ptr objects can be accessed using mutable operations, such as operator= or reset
, simultaneously by multiple threads, even when these instances are copies, and share the same control block internally.
(p, expected, desired, std::memory_order_seq_cst,
std::memory_order_seq_cst ).
(p, expected, desired, std::memory_order_seq_cst,
std::memory_order_seq_cst ).
- If they are equivalent (store the same pointer value, and either share ownership of the same object or are both empty), assigns desired into *p using the memory ordering constraints specified by success and returns true.
- If they are not equivalent, assigns *p into *expected using the memory ordering constraints specified by failure and returns false.
atomic_compare_exchange_weak_explicit
may fail spuriously.If p is a null pointer, the behaviors of these functions are all undefined.
[edit] Parameters
[edit] Exceptions
These functions do not throw exceptions.
[edit] Return value
[edit] Notes
These functions are typically implemented using mutexes, stored in a global hash table where the pointer value is used as the key.
The Concurrency TS offers atomic smart pointer classes atomic_shared_ptr
and atomic_weak_ptr
as a replacement for the use of these functions.
These functions were deprecated in favor of the specializations of the std::atomic template: std::atomic <std::shared_ptr > and std::atomic <std::weak_ptr >.
(since C++20)(until C++26)
These functions were removed in favor of the specializations of the std::atomic template: std::atomic <std::shared_ptr > and std::atomic <std::weak_ptr >.
(since C++26)[edit] Example
Reason: no example
[edit] Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR | Applied to | Behavior as published | Correct behavior |
---|---|---|---|
LWG 2172 | C++11 | expected could be a null pointer | the behavior is undefined in this case |
LWG 2980 | C++11 | empty shared_ptr s were never equivalent
|
equivalent if they store the same pointer value |
[edit] See also
(function template) [edit]
(function template) [edit]
(function template) [edit]