[libcxx] [test] Extend the UNSUPPORTED lines in strong_order_long_double.verify.cpp for non-x86_64 WindowsDifferential Revision: https://reviews.llvm.org/D124992
[libc++] Replace _LIBCPP_HAS_NO_CONCEPTS with _LIBCPP_STD_VER > 17. NFCI.All supported compilers that support C++20 now support concepts. So, remove`_LIB_LIBCPP_HAS_NO_CONCEPTS` in favor of `_LIBC
[libc++] Replace _LIBCPP_HAS_NO_CONCEPTS with _LIBCPP_STD_VER > 17. NFCI.All supported compilers that support C++20 now support concepts. So, remove`_LIB_LIBCPP_HAS_NO_CONCEPTS` in favor of `_LIBCPP_STD_VER > 17`. Similarly inthe tests, remove `// UNSUPPORTED: libcpp-no-concepts`.Differential Revision: https://reviews.llvm.org/D121528
show more ...
[libcxx][CI] Set Arm triples to match native clang build's defaultWe were using:armv8-linux-gnueabihfBut for a native clang build the default target is:armv8l-linux-gnueabihf(ditto for v7)Ad
[libcxx][CI] Set Arm triples to match native clang build's defaultWe were using:armv8-linux-gnueabihfBut for a native clang build the default target is:armv8l-linux-gnueabihf(ditto for v7)Add the "l" to the target triples and update the one testthat is unsupported to look for the various possible names.armv(7 or 8)(m or l, optionally)The UNSUPPORTED does not include aarch64 because aarch64 Linux(and others that follow Arm's AAPCS64) use quad precision forlong double where arm64 (darwin) does not:https://developer.apple.com/documentation/xcode/writing-arm64-code-for-apple-platformshttps://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst#811arithmetic-typesReviewed By: rovkaDifferential Revision: https://reviews.llvm.org/D119948
[libc++] [P1614] Implement the second half of [cmp.alg]: compare_{strong,weak,partial}_fallback.The tests for these are just copy-pasted from the tests for std::{strong,weak,partial}_order,and the
[libc++] [P1614] Implement the second half of [cmp.alg]: compare_{strong,weak,partial}_fallback.The tests for these are just copy-pasted from the tests for std::{strong,weak,partial}_order,and then I added an extra clause in each (test_2()) to test the stuff that's not just the sameas std::*_order.This also includes the fix for https://wg21.link/LWG3465 (which falls naturally out of the"you must write it three times" style, but I've added test cases for it also).There is an action item here to go back and give good diagnostics for SFINAE failuresin these CPOs. I've filed this as https://github.com/llvm/llvm-project/issues/53456 .Differential Revision: https://reviews.llvm.org/D111514
[libcxx][test] `_VSTD` doesn't belong in test code
[libc++] Handle armv7m in two architecture dependent tests
[libc++] [P1614] Implement [cmp.alg]'s std::{strong,weak,partial}_order.This does not include `std::compare_*_fallback`; those are coming later.There's still an open question of how to implement
[libc++] [P1614] Implement [cmp.alg]'s std::{strong,weak,partial}_order.This does not include `std::compare_*_fallback`; those are coming later.There's still an open question of how to implement std::strong_orderfor `long double`, which has 80 value bits and 48 padding bits on x86-64,and which is presumably *not* IEEE 754-compliant on PPC64 and so on.So that part is left unimplemented.Differential Revision: https://reviews.llvm.org/D110738