RRaul Tambre[libc++] Undeprecate ATOMIC_FLAG_INIT (LWG3659)
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] [test] Qualify calls to std::atomic_flag_{clear,test} functions. NFCI. We shouldn't be calling these functions via ADL -- and neither should anybody in the wild be calling it via ADL, so it's not like we need to test the ADL ability of these functions in particular. Reviewed as part of D119860. | 4 年前 | |
[libc++] Enable <atomic> when threads are disabled std::atomic is, for the most part, just a thin veneer on top of compiler builtins. Hence, it should be available even when threads are not available on the system, and in fact there has been requests for such support. This patch: - Moves __libcpp_thread_poll_with_backoff to its own header so it can be used in <atomic> when threads are disabled. - Adds a dummy backoff policy for atomic polling that doesn't know about threads. - Adjusts the <atomic> feature-test macros so they are provided even when threads are disabled. - Runs the <atomic> tests when threads are disabled. rdar://77873569 Differential Revision: https://reviews.llvm.org/D114109 | 4 年前 | |
[libc++] Remove workaround for .fail.cpp tests that don't have clang-verify markup By renaming .fail.cpp tests that don't need clang-verify to .compile.fail.cpp, the new test format will not try to compile these tests with clang-verify, and the old test format will work just the same. However, this allows removing a workaround that requires parsing each test looking for clang-verify markup. After this change, a .fail.cpp test should always have clang-verify markup. When clang-verify is not supported by the compiler, we will just check that these tests fail to compile. When clang-verify is supported, these tests will be compiled with clang-verify whether they have markup or not (so they should have markup, or they will fail). This simplifies the test suite and also ensures that all of our .fail.cpp tests provide clang-verify markup. If it's impossible for a test to have clang-verify markup, it can be moved to a .compile.fail.cpp test, which are unconditionally just checked for compilation failure. | 6 年前 | |
[libc++] Remove workaround for .fail.cpp tests that don't have clang-verify markup By renaming .fail.cpp tests that don't need clang-verify to .compile.fail.cpp, the new test format will not try to compile these tests with clang-verify, and the old test format will work just the same. However, this allows removing a workaround that requires parsing each test looking for clang-verify markup. After this change, a .fail.cpp test should always have clang-verify markup. When clang-verify is not supported by the compiler, we will just check that these tests fail to compile. When clang-verify is supported, these tests will be compiled with clang-verify whether they have markup or not (so they should have markup, or they will fail). This simplifies the test suite and also ensures that all of our .fail.cpp tests provide clang-verify markup. If it's impossible for a test to have clang-verify markup, it can be moved to a .compile.fail.cpp test, which are unconditionally just checked for compilation failure. | 6 年前 | |
[libc++] Remove workaround for .fail.cpp tests that don't have clang-verify markup By renaming .fail.cpp tests that don't need clang-verify to .compile.fail.cpp, the new test format will not try to compile these tests with clang-verify, and the old test format will work just the same. However, this allows removing a workaround that requires parsing each test looking for clang-verify markup. After this change, a .fail.cpp test should always have clang-verify markup. When clang-verify is not supported by the compiler, we will just check that these tests fail to compile. When clang-verify is supported, these tests will be compiled with clang-verify whether they have markup or not (so they should have markup, or they will fail). This simplifies the test suite and also ensures that all of our .fail.cpp tests provide clang-verify markup. If it's impossible for a test to have clang-verify markup, it can be moved to a .compile.fail.cpp test, which are unconditionally just checked for compilation failure. | 6 年前 | |
[libc++] Enable <atomic> when threads are disabled std::atomic is, for the most part, just a thin veneer on top of compiler builtins. Hence, it should be available even when threads are not available on the system, and in fact there has been requests for such support. This patch: - Moves __libcpp_thread_poll_with_backoff to its own header so it can be used in <atomic> when threads are disabled. - Adds a dummy backoff policy for atomic polling that doesn't know about threads. - Adjusts the <atomic> feature-test macros so they are provided even when threads are disabled. - Runs the <atomic> tests when threads are disabled. rdar://77873569 Differential Revision: https://reviews.llvm.org/D114109 | 4 年前 | |
[libc++] Undeprecate ATOMIC_FLAG_INIT (LWG3659) According to @aaron.ballman this was marked Tentatively Ready as of 2022-07-07. D129362 implemented the C counterpart. Reviewed By: ldionne, #libc, Mordante Differential Revision: https://reviews.llvm.org/D129380 | 3 年前 | |
[libc++] Enable <atomic> when threads are disabled std::atomic is, for the most part, just a thin veneer on top of compiler builtins. Hence, it should be available even when threads are not available on the system, and in fact there has been requests for such support. This patch: - Moves __libcpp_thread_poll_with_backoff to its own header so it can be used in <atomic> when threads are disabled. - Adds a dummy backoff policy for atomic polling that doesn't know about threads. - Adjusts the <atomic> feature-test macros so they are provided even when threads are disabled. - Runs the <atomic> tests when threads are disabled. rdar://77873569 Differential Revision: https://reviews.llvm.org/D114109 | 4 年前 |