diff options
| author | ZENG Hao <c@cyano.cn> | 2025-04-20 17:02:16 +0800 |
|---|---|---|
| committer | Jonathan Wakely <redi@gcc.gnu.org> | 2025-05-06 12:53:53 +0100 |
| commit | f2a69ee64f8b663d14649b7475edb8e09e83db1b (patch) | |
| tree | 446e064bc62eb3b4d463a7eec2b8b8d47b485337 /gcc | |
| parent | a14d65f81e18e70144ceddfc3142a8103984919d (diff) | |
| download | gcc-f2a69ee64f8b663d14649b7475edb8e09e83db1b.zip gcc-f2a69ee64f8b663d14649b7475edb8e09e83db1b.tar.gz gcc-f2a69ee64f8b663d14649b7475edb8e09e83db1b.tar.bz2 | |
libstdc++: fix possible undefined atomic lock-free type aliases in module std
When building for 'i386-*' targets, all basic types are 'sometimes lock-free'
and thus std::atomic_signed_lock_free and std::atomic_unsigned_lock_free are
not declared. In the header <atomic>, they are placed in preprocessor
condition __cpp_lib_atomic_lock_free_type_aliases. In module std, they should
be the same.
libstdc++-v3/ChangeLog:
* src/c++23/std.cc.in (atomic_signed_lock_free): Guard with
preprocessor check for __cpp_lib_atomic_lock_free_type_aliases.
(atomic_unsigned_lock_free): Likewise.
(cherry picked from commit 466c80a885ccbd5186cd57b0785cf38b8cf2ff2f)
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions