dev_17.0.6

TTobias Hieta[libc++][print] Make <print> tests require file system support.

1d07708c创建于 2023年8月7日历史提交

文件	最后提交记录	最后更新时间
cmp	[libc++] Add annotation for arm64e in the strong_order test for long double As a fly-by, improve readability by giving a bit more space to some comments.	3 年前
cstdint	[libc++] Add an option to disable wide character support in libc++ Some embedded platforms do not wish to support the C library functionality for handling wchar_t because they have no use for it. It makes sense for libc++ to work properly on those platforms, so this commit adds a carve-out of functionality for wchar_t. Unfortunately, unlike some other carve-outs (e.g. random device), this patch touches several parts of the library. However, despite the wide impact of this patch, I still think it is important to support this configuration since it makes it much simpler to port libc++ to some embedded platforms. Differential Revision: https://reviews.llvm.org/D111265	4 年前
support.coroutines	[libc++] Qualifies size_t. This has been done using the following command find libcxx/test -type f -exec perl -pi -e 's|^([^/]+?)((?<!::)size_t)|\1std::\2|' \{} \; And manually removed some false positives in std/depr/depr.c.headers. The std module doesn't export ::size_t, this is a preparation for that module. Reviewed By: ldionne, #libc, EricWF, philnik Differential Revision: https://reviews.llvm.org/D146088	3 年前
support.dynamic	[libc++] Stop running backdeployment CI on macOS 10.9 The oldest deployment target supported by Xcode 14 is macOS 10.13. Trying to back-deploy to older targets runs into other issues in Clang, so stop testing libc++ against unsupported deployment targets. This patch doesn't attempt to clean up support for older deployment targets from the code base -- this will be done in a follow-up patch. Differential Revision: https://reviews.llvm.org/D155085	3 年前
support.exception	[libc++] Use the stdlib=<LIB> Lit feature instead of use_system_cxx_lib The use_system_cxx_lib Lit feature was only used for back-deployment testing. However, one immense hole in that setup was that we didn't have a proper way to test Apple's own libc++ outside of back-deployment, which was embodied by the fact that we needed to define _LIBCPP_DISABLE_AVAILABILITY when testing (see change in libcxx/utils/libcxx/test/params.py). This led to the apple-system testing configuration not checking for availability markup, which is obviously quite bad since the library we ship actually has availability markup. Using stdlib=<VENDOR>-libc++ instead to encode back-deployment restrictions on tests is simpler and it makes it possible to naturally support tests such as availability markup checking even in the tip-of-trunk Apple-libc++ configuration. Differential Revision: https://reviews.llvm.org/D146366	3 年前
support.general	Support tests in freestanding Summary: Freestanding is *weird*. The standard allows it to differ in a bunch of odd manners from regular C++, and the committee would like to improve that situation. I'd like to make libc++ behave better with what freestanding should be, so that it can be a tool we use in improving the standard. To do that we need to try stuff out, both with "freestanding the language mode" and "freestanding the library subset". Let's start with the super basic: run the libc++ tests in freestanding, using clang as the compiler, and see what works. The easiest hack to do this: In utils/libcxx/test/config.py add: self.cxx.compile_flags += ['-ffreestanding'] Run the tests and they all fail. Why? Because in freestanding main isn't special. This "not special" property has two effects: main doesn't get mangled, and main isn't allowed to omit its return statement. The first means main gets mangled and the linker can't create a valid executable for us to test. The second means we spew out warnings (ew) and the compiler doesn't insert the return we omitted, and main just falls of the end and does whatever undefined behavior (if you're luck, ud2 leading to non-zero return code). Let's start my work with the basics. This patch changes all libc++ tests to declare main as int main(int, char** so it mangles consistently (enabling us to declare another extern "C" main for freestanding which calls the mangled one), and adds return 0; to all places where it was missing. This touches 6124 files, and I apologize. The former was done with The Magic Of Sed. The later was done with a (not quite correct but decent) clang tool: https://gist.github.com/jfbastien/793819ff360baa845483dde81170feed This works for most tests, though I did have to adjust a few places when e.g. the test runs with -x c, macros are used for main (such as for the filesystem tests), etc. Once this is in we can create a freestanding bot which will prevent further regressions. After that, we can start the real work of supporting C++ freestanding fairly well in libc++. <rdar://problem/47754795> Reviewers: ldionne, mclow.lists, EricWF Subscribers: christof, jkorous, dexonsmith, arphaman, miyuki, libcxx-commits Differential Revision: https://reviews.llvm.org/D57624 llvm-svn: 353086	7 年前
support.initlist	[libc++] NFC: Normalize #endif // comment indentation	5 年前
support.limits	[libc++][print] Make <print> tests require file system support. print functions require FILE and stdout to be available and cause compilation errors on platforms that don't support the file system. Differential Revision: https://reviews.llvm.org/D156585 (cherry picked from commit 1cf970db4e5499f6b38d9c6644935a78d758802c)	2 年前
support.rtti	[libc++] Implement P1328R1 constexpr std::type_info::operator== Differential Revision: https://reviews.llvm.org/D143447	3 年前
support.runtime	[libc++] Use the stdlib=<LIB> Lit feature instead of use_system_cxx_lib The use_system_cxx_lib Lit feature was only used for back-deployment testing. However, one immense hole in that setup was that we didn't have a proper way to test Apple's own libc++ outside of back-deployment, which was embodied by the fact that we needed to define _LIBCPP_DISABLE_AVAILABILITY when testing (see change in libcxx/utils/libcxx/test/params.py). This led to the apple-system testing configuration not checking for availability markup, which is obviously quite bad since the library we ship actually has availability markup. Using stdlib=<VENDOR>-libc++ instead to encode back-deployment restrictions on tests is simpler and it makes it possible to naturally support tests such as availability markup checking even in the tip-of-trunk Apple-libc++ configuration. Differential Revision: https://reviews.llvm.org/D146366	3 年前
support.srcloc	[libc++] Removes Clang 14 support. Per our policy we only support the last two releases. Reviewed By: #libc, EricWF, philnik Differential Revision: https://reviews.llvm.org/D148359	3 年前
support.start.term	[libc++] Fix XFAIL annotation The triple can sometimes be arm64-apple-macos, where the previous XFAIL annotation wouldn't match (and hence the test would fail unexpectedly).	4 年前
support.types	[libc++] Qualifies ptrdiff_t and max_align_t. This has been done using the following commands find libcxx/test -type f -exec perl -pi -e 's|^([^/]+?)((?<!::)ptrdiff_t)|\1std::\2|' \{} \; find libcxx/test -type f -exec perl -pi -e 's|^([^/]+?)((?<!::)max_align_t)|\1std::\2|' \{} \; The std module doesn't export declarations in the global namespaace., This is a preparation for that module. Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D146550	3 年前