diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2022-05-17 16:17:21 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2022-05-17 20:53:40 +0100 |
| commit | ddb1427defe95341ac2eb672e7bea7303f8c7db9 (patch) | |
| tree | 90c89ddc1745b295c25b34ea1d879f4fb6f556c2 /gcc | |
| parent | 5c2d703e6d6d47f41635ca4df06c555010462081 (diff) | |
| download | gcc-ddb1427defe95341ac2eb672e7bea7303f8c7db9.zip gcc-ddb1427defe95341ac2eb672e7bea7303f8c7db9.tar.gz gcc-ddb1427defe95341ac2eb672e7bea7303f8c7db9.tar.bz2 | |
libstdc++: Relax memory ordering for default memory resource object
Currently pmr::set_default_resource and pmr::get_default_resource both
use sequentially consistent memory ordering. This is overkill. The
standard only requires that a call to set_default_resource synchronizes
with subsequent calls to set_default_resource and get_default_resource.
Using acquire-release for the setter and acquire for the getter is
sufficient to meet the requirement.
Reviewed-by: Thomas Rodgers <trodgers@redhat.com>
libstdc++-v3/ChangeLog:
* src/c++17/memory_resource.cc (set_default_resource): Use
memory_order_acq_rel.
(get_default_resource): Use memory_order_acquire.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions