Changes in valarray

ac1d560709d2ecfe83a98285d4a13afae6db4316 - [libc++][hardening] Add a bounds check for `valarray` and `bitset`. (#120685)

Wed, 25 Dec 2024 02:22:18 +0000

[libc++][hardening] Add a bounds check for `valarray` and `bitset`. (#120685)Add a `valid-element-access` check to `valarray::operator[]` and `bitset::operator[]`. List of files: /llvm-project/libcxx/include/valarray

b9a2658a3e8bd13b0f9e7a8a440832a95b377216 - [libc++][C++03] Use `__cxx03/` headers in C++03 mode (#109002)

Sat, 21 Dec 2024 12:01:48 +0000

[libc++][C++03] Use `__cxx03/` headers in C++03 mode (#109002)This patch implements the forwarding to frozen C++03 headers asdiscussed inhttps://discourse.llvm.org/t/rfc-freezing-c-03-headers-in-libc. In theRFC, we initially proposed selecting the right headers from the Clangdriver, however consensus seemed to steer towards handling this in thelibrary itself. This patch implements that direction.At a high level, the changes basically amount to making each publicheader look like this:```// inside #ifdef _LIBCPP_CXX03_LANG# include <__cxx03/vector>#else // normal content#endif```In most cases, public headers are simple umbrella headers so there isn'tmuch code in the #else branch. In other cases, the #else branch containsthe actual implementation of the header. List of files: /llvm-project/libcxx/include/valarray

59890c13343af9e308281b3c76bac425087f4f8a - [libc++] Granularize includes (#119964)

Tue, 17 Dec 2024 10:29:16 +0000

[libc++] Granularize includes (#119964) List of files: /llvm-project/libcxx/include/valarray

c166a9c713ec86b86f1f178a5133bc128fd0a610 - [libc++] Add #if 0 block to all the top-level headers (#119234)

Tue, 10 Dec 2024 15:02:12 +0000

[libc++] Add #if 0 block to all the top-level headers (#119234)Including The frozen C++03 headers results in a lot of formattingchanges in the main headers, so this splits these changes into aseparate commit instead.This is part ofhttps://discourse.llvm.org/t/rfc-freezing-c-03-headers-in-libc. List of files: /llvm-project/libcxx/include/valarray

e99c4906e44ae3f921fa05356909d006cda8d954 - [libc++] Granularize includes (#108696)

Thu, 31 Oct 2024 01:20:10 +0000

[libc++] Granularize includes (#108696) List of files: /llvm-project/libcxx/include/valarray

ba87515fea90b5d55836a8e3be63a7e683ce299d - [libc++][RFC] Always define internal feature test macros (#89178)

Sat, 12 Oct 2024 07:49:52 +0000

[libc++][RFC] Always define internal feature test macros (#89178)Currently, the library-internal feature test macros are only defined if the feature is not available, and always have the prefix `_LIBCPP_HAS_NO_`. This patch changes that, so that they are always defined and have the prefix `_LIBCPP_HAS_` instead. This changes the canonical use of these macros to `#if _LIBCPP_HAS_FEATURE`, which means that using an undefined macro (e.g. due to a missing include) is diagnosed now. While this is rather unlikely currently, a similar change in `<__configuration/availability.h>` caught a few bugs. This also improves readability, since it removes the double-negation of `#ifndef _LIBCPP_HAS_NO_FEATURE`. The current patch only touches the macros defined in `<__config>`. If people are happy with this approach, I'll make a follow-up PR to also change the macros defined in `<__config_site>`. List of files: /llvm-project/libcxx/include/valarray

e2c2ffbe7a1b5d9e32a2ce64279475b50c4cba5b - [libc++][NFC] Run clang-format on libcxx/include again (#95874)

Tue, 18 Jun 2024 13:13:45 +0000

[libc++][NFC] Run clang-format on libcxx/include again (#95874)As time went by, a few files have become mis-formatted w.r.t. clang-format. This was made worse by the fact that formatting was not being enforced in extensionless headers. This commit simply brings all of libcxx/include in-line with clang-format again. We might have to do this from time to time as we update our clang-format version, but frankly this is really low effort now that we've formatted everything once. List of files: /llvm-project/libcxx/include/valarray

37dca605c9bd41732da010ee97ed15ad9585a37d - [libc++] Clean up includes of <__assert> (#80091)

Thu, 29 Feb 2024 15:12:22 +0000

[libc++] Clean up includes of <__assert> (#80091)Originally, we used __libcpp_verbose_abort to handle assertion failures. That function was declared from all public headers. Since we don't use that mechanism anymore, we don't need to declare __libcpp_verbose_abort from all public headers, and we can clean up a lot of unnecessary includes. This patch also moves the definition of the various assertion categories to the <__assert> header, since we now rely on regular IWYU for these assertion macros. rdar://105510916 List of files: /llvm-project/libcxx/include/valarray

3e33b6f5de6905c98395a77b41d474b87ef9e677 - [libc++][NFC] Reformat a few files that had gotten mis-formatted

Thu, 08 Feb 2024 15:11:39 +0000

[libc++][NFC] Reformat a few files that had gotten mis-formattedThose appear to be oversights when committing patchesin the last few months. List of files: /llvm-project/libcxx/include/valarray

5ca2777c69f8708d583e230c56ac7f5f6376fb40 - [libc++] Fixes valarray proxy type compound assignment operations. (#76528)

Sat, 03 Feb 2024 16:23:31 +0000

[libc++] Fixes valarray proxy type compound assignment operations. (#76528)The valarray<>::operator[](...) const functions return proxy objects. The valarray<>::operator[](...) functions return valarray objects. However the standard allows functions returning valarray objects to return custom proxy objects instead. Libc++ returns __val_expr proxies. Functions taking a valarray object must work with the custom proxies too. Therefore several operations have a custom proxy overload instead of valarray overloads. Libc++ doesn't specify a valarray overload. This is an issue with the standard proxy types; these can implicitly be converted to a valarray. The solution is to allow the standard proxies to behave as-if they are custom proxies. This patch fixes the valarray compound assignments. Other operations, like the binary non-member functions are not fixed. These will be done in a followup patch. Fixes: https://github.com/llvm/llvm-project/issues/21320 List of files: /llvm-project/libcxx/include/valarray

9783f28cbb155e4a8d49c12e1c60ce14dcfaf0c7 - [libc++] Format the code base (#74334)

Mon, 18 Dec 2023 19:01:33 +0000

[libc++] Format the code base (#74334)This patch runs clang-format on all of libcxx/include and libcxx/src, in accordance with the RFC discussed at [1]. Follow-up patches will format the benchmarks, the test suite and remaining parts of the code. I'm splitting this one into its own patch so the diff is a bit easier to review. This patch was generated with: find libcxx/include libcxx/src -type f \ | grep -v 'module.modulemap.in' \ | grep -v 'CMakeLists.txt' \ | grep -v 'README.txt' \ | grep -v 'libcxx.imp' \ | grep -v '__config_site.in' \ | xargs clang-format -i A Git merge driver is available in libcxx/utils/clang-format-merge-driver.sh to help resolve merge and rebase issues across these formatting changes. [1]: https://discourse.llvm.org/t/rfc-clang-formatting-all-of-libc-once-and-for-all List of files: /llvm-project/libcxx/include/valarray

77a00c0d546cd4aa8311b5b9031ae9ea8cdb050c - [libc++] Replace uses of _VSTD:: by std:: (#74331)

Tue, 05 Dec 2023 16:19:15 +0000

[libc++] Replace uses of _VSTD:: by std:: (#74331)As part of the upcoming clang-formatting of libc++, this patch performs the long desired removal of the _VSTD macro. See https://discourse.llvm.org/t/rfc-clang-formatting-all-of-libc-once-and-for-all for the clang-format proposal. List of files: /llvm-project/libcxx/include/valarray

4c198542226223f6a5c5511a1f89b37d15ee10b9 - [libc++] Rename _LIBCPP_INLINE_VISIBILITY to _LIBCPP_HIDE_FROM_ABI (#74095)

Mon, 04 Dec 2023 15:25:14 +0000

[libc++] Rename _LIBCPP_INLINE_VISIBILITY to _LIBCPP_HIDE_FROM_ABI (#74095)In preparation for running clang-format on the whole code base, we are also removing mentions of the legacy _LIBCPP_INLINE_VISIBILITY macro in favor of the newer _LIBCPP_HIDE_FROM_ABI. We're still leaving the definition of _LIBCPP_INLINE_VISIBILITY to avoid creating needless breakage in case some older patches are checked-in with mentions of the old macro. After we branch for LLVM 18, we can do another pass to clean up remaining uses of the macro that might have gotten introduced by mistake (if any) and remove the macro itself at the same time. This is just a minor convenience to smooth out the transition as much as possible. See https://discourse.llvm.org/t/rfc-clang-formatting-all-of-libc-once-and-for-all for the clang-format proposal. List of files: /llvm-project/libcxx/include/valarray

475bd19ee8e42e68635b9770d5725461b7300914 - [libc++][NFC] Refactor return type enable_ifs to defaulted template arguments

Tue, 15 Aug 2023 19:19:05 +0000

[libc++][NFC] Refactor return type enable_ifs to defaulted template argumentsThis brings most of the enable_ifs in libc++ to the same style. It also has the nice side-effect of reducing the size of names of these symbols, since the depedent return type is shorter.Reviewed By: #libc, ldionneSpies: ldionne, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D157736 List of files: /llvm-project/libcxx/include/valarray

f1ea0b11ca03d0f8b5785b7ec92d2eb673eeb4b9 - [libc++] Merge _LIBCPP_FUNC_VIS, _LIBCPP_TYPE_VIS and _LIBCPP_EXCEPTION_ABI into _LIBCPP_EXPORTED_FROM_ABI

Wed, 14 Jun 2023 17:17:50 +0000

[libc++] Merge _LIBCPP_FUNC_VIS, _LIBCPP_TYPE_VIS and _LIBCPP_EXCEPTION_ABI into _LIBCPP_EXPORTED_FROM_ABIThese macros are always defined identically, so we can simplify the code a bit by merging them.Reviewed By: ldionne, #libcSpies: libcxx-commits, krytarowski, smeenaiDifferential Revision: https://reviews.llvm.org/D152652 List of files: /llvm-project/libcxx/include/valarray

f877e88c354eacba1db81b82270ff8c27f000ea6 - [libc++][spaceship] P1614R2: Added `operator==` to `slice`

Sat, 10 Jun 2023 10:58:56 +0000

[libc++][spaceship] P1614R2: Added `operator==` to `slice`Implements parts of P1614R2:- Added `operator==` to `slice`Reviewed By: #libc, MordanteDifferential Revision: https://reviews.llvm.org/D152617 List of files: /llvm-project/libcxx/include/valarray

91121ea6dc123733100d54622c9e89b1f6e89126 - [libc++][PSTL] Reduce the amount of transitive includes

Tue, 02 May 2023 16:45:37 +0000

[libc++][PSTL] Reduce the amount of transitive includesReviewed By: ldionne, #libcSpies: libcxx-commits, miyukiDifferential Revision: https://reviews.llvm.org/D149599 List of files: /llvm-project/libcxx/include/valarray

2d7bb01840067d2b9f6b02bd633ca914d513544b - [NFC][libc++] Removes incorrect sliceExpr friend.

Sat, 15 Apr 2023 15:01:38 +0000

[NFC][libc++] Removes incorrect sliceExpr friend.There is no type named sliceExpr, so it's likely a misspelling ofeither slice_array or __slice_expr. Neither of which appear toneed the friend declaration.This may indicate a unimplemented bit of `

e13c43b229527234ec99f7f03aff3e1560c259c8 - Revert "[NFC][libc++] Removes sliceExpr friend."

Sat, 15 Apr 2023 14:56:50 +0000

Revert "[NFC][libc++] Removes sliceExpr friend."This reverts commit d5193e34b81fb3e9c27aea541516112d8a5f708d.Reverted at @EricWF's request so it can be relanded with a better commitmessage. List of files: /llvm-project/libcxx/include/valarray

d5193e34b81fb3e9c27aea541516112d8a5f708d - [NFC][libc++] Removes sliceExpr friend.

Fri, 14 Apr 2023 18:00:51 +0000

[NFC][libc++] Removes sliceExpr friend.The class is never defined. This was discovered while validating modulesin libc++.Reviewed By: #libc, philnikDifferential Revision: https://reviews.llvm.org/D148357 List of files: /llvm-project/libcxx/include/valarray