| [libc++] Take advantage of -fexperimental-library in libc++ When -fexperimental-library is passed, libc++ will now pick up the appropriate __has_feature flag defined by Clang to enable the experimental library features. As a fly-by, also update the documentation for the various TSes. Differential Revision: https://reviews.llvm.org/D130176 | 3 年前 |
| [libc++][doc] Use issue labels. During the review of D111166 I had a private discussion with @ldionne to avoid the duplication of the C++2b issues in the Ranges and Format status pages. The main reason for duplicating them is to make it easier to find them. The title of the paper may not always make it clear to which project the paper belongs. This commit removes all LWG-issues from the Ranges and Format status page and adds labels for these issue in the C++20/C++23 issues list. A quick scan revealed there are some issues that are missing a label since they weren't on the ranges issue list. These can be labelled in a separate commit. In that commit I'll also look for issues for the spaceship operator and chrono. Reviewed By: Quuxplusone, ldionne, #libc Differential Revision: https://reviews.llvm.org/D111458 | 4 年前 |
| [libc++][format] Exposes basic-format-string This paper was accepted during the last plenary and is intended to be backported to LLVM 15. When backporting the release notes in the branch should be updated too. Note the feature-test macro isn't updated since this will change; three papers have updated the same macro in the same plenary. Implements: - P2508R1 Exposing std::basic-format-string Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D130643 (cherry picked from commit f712775dafdb221fdf73f38819fa9e618aec6b67) | 3 年前 |
| [libc++] Add timeout to BuildKite jobs We just had a case where a build bot stalled in an infinite loop during testing, and the whole pipeline got stuck. To avoid that from happening in the future, use a timeout on BuildKite jobs. Differential Revision: https://reviews.llvm.org/D107765 | 4 年前 |
| [libc++] Treat incomplete features just like other experimental features In particular remove the ability to expel incomplete features from the library at configure-time, since this can now be done through the _LIBCPP_ENABLE_EXPERIMENTAL macro. Also, never provide symbols related to incomplete features inside the dylib, instead provide them in c++experimental.a (this changes the symbols list, but not for any configuration that should have shipped). Differential Revision: https://reviews.llvm.org/D128928 | 3 年前 |
| docs: Fix Sphinx detection with out-of-tree builds Adapt to changes made in r302499. llvm-svn: 302517 | 8 年前 |
| [libc++] Treat incomplete features just like other experimental features In particular remove the ability to expel incomplete features from the library at configure-time, since this can now be done through the _LIBCPP_ENABLE_EXPERIMENTAL macro. Also, never provide symbols related to incomplete features inside the dylib, instead provide them in c++experimental.a (this changes the symbols list, but not for any configuration that should have shipped). Differential Revision: https://reviews.llvm.org/D128928 | 3 年前 |
| [libc++][format] Updates feature-test macros. During the discussion on the SG-10 mailinglist regarding the format feature-test macros voted in during the last plenary it turns out libc++ can't mark the format feature-test macro as implemented. According to https://isocpp.org/std/standing-documents/sd-6-sg10-feature-test-recommendations#__cpp_lib_format the not yet implemented paper P1361R2 Integration of chrono with text formatting affects the feature test macro. Note that P1361R2 doesn't mention the feature-test macro nor is there an LWG-issue to address the issue. The reporter of the issue didn't recall where this requirement exactly has been decided. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D133271 | 3 年前 |
| [libc++] NFC: Add note about how the libcxx website gets updated | 4 年前 |
| [libc++] Keep unary_function and binary_function in C++17 for one more release In LLVM 15, we added the deprecation markup for unary_function and binary_function for >= C++11, and we also removed it for >= C++17. While this is in accordance with the Standard, it's also a bit quick for our users, since there was no release in which the classes were marked as deprecated before their removal. We noticed widespread breakage due to this, and after months of trying to fix downstream failures, I am coming to the conclusion that users will be better served if we give them one release where unary_function is deprecated but still provided even in >= C++17. Differential Revision: https://reviews.llvm.org/D134473 | 3 年前 |
| [libc++] More documentation improvements about running tests (cherry picked from commit 3d5d44269c933849068c073f356002940f85bce4) | 3 年前 |
| [libc++] Allow enabling assertions when back-deploying When back-deploying to older platforms, we can still provide assertions, but we might not be able to provide a great implementation for the verbose handler. Instead, we can just call ::abort(). Differential Revision: https://reviews.llvm.org/D131199 (cherry picked from commit e36f9e13bca41223bd6af7e49bf020e58a676e9d) | 3 年前 |
| Bump the trunk major version to 15 | 4 年前 |
| [libc++][CI] Updates GCC to version 12. Reviewed By: ldionne, philnik, #libc, #libc_abi Differential Revision: https://reviews.llvm.org/D126667 | 3 年前 |