From: Jonathan Wakely Date: Tue, 21 May 2019 13:50:35 +0000 (+0100) Subject: Fix names of _Lock_policy constants in libstdc++ manual X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=049f115abb8dbb847762c1348c583ece886c0a32;p=gcc.git Fix names of _Lock_policy constants in libstdc++ manual * doc/xml/manual/shared_ptr.xml: Fix names of lock policy constants. From-SVN: r271465 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 79318f762d8..90708f98025 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,7 @@ +2019-05-21 Jonathan Wakely + + * doc/xml/manual/shared_ptr.xml: Fix names of lock policy constants. + 2019-05-20 Thomas Rodgers PR libstdc++/90252 diff --git a/libstdc++-v3/doc/xml/manual/shared_ptr.xml b/libstdc++-v3/doc/xml/manual/shared_ptr.xml index fcbade6d5bf..24e275e95eb 100644 --- a/libstdc++-v3/doc/xml/manual/shared_ptr.xml +++ b/libstdc++-v3/doc/xml/manual/shared_ptr.xml @@ -239,7 +239,7 @@ available policies are: - _S_Atomic + _S_atomic Selected when GCC supports a builtin atomic compare-and-swap operation @@ -252,7 +252,7 @@ synchronisation. - _S_Mutex + _S_mutex The _Sp_counted_base specialization for this policy contains a mutex, @@ -263,7 +263,7 @@ builtins aren't available so explicit memory barriers are needed in places. - _S_Single + _S_single This policy uses a non-reentrant add_ref_lock() with no locking. It is