libc++ was previously a bit confused by what the value of __cpp_concepts
should be. Also replaces __floating_point with floating_point now
that it exists.
Details
- Reviewers
ldionne miscco EricWF CaseyCarter Mordante curdeius - Group Reviewers
Restricted Project - Commits
- rGe4dd614ae811: [libcxx] cleans up __cpp_concepts mess
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
libcxx/test/std/language.support/support.limits/support.limits.general/version.version.pass.cpp | ||
---|---|---|
2886 | Could we clean that up to use!__LIBCPP_HAS_NO_CONCEPTS |
It seems this fails to build on Apple due to an issue in _LIBCPP_HAS_NO_CONCEPTS. I'll fix that in main this weekend.
1a5c92f68021 should fix this patch. Can you rebase on main to see whether the CI passes for this patch?
libcxx/include/concepts | ||
---|---|---|
152 | I see !_LIBCPP_HAS_NO_CONCEPTS instead of !defined(_LIBCPP_HAS_NO_CONCEPTS) at several places in this patch. Probably part of the new build failures. |
libcxx/include/numbers | ||
---|---|---|
103–115 | Assuming you didn't change the value of these constants :-) |
@cjdb, after this landed and then @zoecarver's D60368 landed on top of it and maybe merge-conflicted with it... I'm now seeing that the feature-test-macro tests that are checked in do not match the output you get by running the libcxx/utils/generate_feature_test_macro_components.py script. Could you (@cjdb) run libcxx/utils/generate_feature_test_macro_components.py locally, check whether it matches what you intended, and if so, check in those changes? (If the generated output doesn't match what you intended, then probably you should post another PR.)
Nice catch! Looking at the diff here, it appears that I didnt' change libcxx/utils/generate_feature_test_macro_components.py properly. Making a patch for it now.
I see !_LIBCPP_HAS_NO_CONCEPTS instead of !defined(_LIBCPP_HAS_NO_CONCEPTS) at several places in this patch. Probably part of the new build failures.