Like we have been doing for libc++ for a while now, start using
from-scratch testing configurations for libc++abi.
As a fly-by fix, remove the LIBCXXABI_NO_TIMER macro, which was defined
but never used.
Paths
| Differential D125242
[libc++abi] Use from-scratch testing configs for libc++abi by default ClosedPublic Authored by ldionne on May 9 2022, 8:57 AM.
Details
Summary Like we have been doing for libc++ for a while now, start using As a fly-by fix, remove the LIBCXXABI_NO_TIMER macro, which was defined
Diff Detail
Unit TestsFailed Event TimelineComment Actions I'm not sure I understand what "from scratch" means given this patch, but I don't need to understand to see that to LGTM it. LGTM once the inline comments are addressed.
This revision is now accepted and ready to land.May 24 2022, 11:28 AM Comment Actions
Yeah, it's not a great name. It's how I've been calling the new style of configuration file where you define only the base Lit substitutions required for your environment instead of using the logic in config.py that tried to handle all configurations (and you'd add various knobs to tweak its behavior instead).
Closed by commit rG851bfc07c86e: [libc++abi] Use from-scratch testing configs for libc++abi by default (authored by ldionne). · Explain WhyMay 26 2022, 6:08 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 431737 libcxxabi/CMakeLists.txt
libcxxabi/test/configs/apple-libc++abi-backdeployment.cfg.in
libcxxabi/test/configs/apple-libc++abi-shared.cfg.in
libcxxabi/test/configs/cmake-bridge.cfg.in
libcxxabi/test/configs/ibm-libc++abi-shared.cfg.in
libcxxabi/test/configs/llvm-libc++abi-merged.cfg.in
libcxxabi/test/configs/llvm-libc++abi-mingw.cfg.in
libcxxabi/test/configs/llvm-libc++abi-shared-clangcl.cfg.in
libcxxabi/test/configs/llvm-libc++abi-shared-gcc.cfg.in
libcxxabi/test/configs/llvm-libc++abi-shared.cfg.in
libcxxabi/test/configs/llvm-libc++abi-static-clangcl.cfg.in
libcxxabi/test/configs/llvm-libc++abi-static.cfg.in
libcxxabi/test/cxa_thread_atexit_test.pass.cpp
libcxxabi/test/forced_unwind3.pass.cpp
libcxxabi/test/guard_test_basic.pass.cpp
libcxxabi/test/guard_threaded_test.pass.cpp
libcxxabi/test/libcxxabi/test/config.py
libcxxabi/test/test_exception_storage.pass.cpplibcxxabi/test/test_fallback_malloc.pass.cpp
libcxxabi/test/test_guard.pass.cpp
libcxxabi/test/thread_local_destruction_order.pass.cpp
|
If we're using the same feature name for libc++ and libc++abi, I assume that means that they cannot vary independently.
If so, should we just use _LIBCPP_HAS_NO_THREADS instead, and kill the LIBCXXABI_HAS_NO_THREADS macro?