[libc++] Remove test-suite annotations for unsupported Clang versionsDifferential Revision: https://reviews.llvm.org/D108471
[libc++] Remove Lit annotations for unsupported GCC versions from the test suiteSince we officially don't support several older compilers now, we candrop a lot of the markup in the test suite. Thi
[libc++] Remove Lit annotations for unsupported GCC versions from the test suiteSince we officially don't support several older compilers now, we candrop a lot of the markup in the test suite. This helps keep the testsuite simple and makes sure that UNSUPPORTED annotations don't rot.This is the first patch of a series that will remove annotations forcompilers that are now unsupported.Differential Revision: https://reviews.llvm.org/D107787
show more ...
[libcxx][nfc] prefixes test type `input_iterator` with `cpp17_`C++20 revised the definition of what it means to be an iterator. Whileall _Cpp17InputIterators_ satisfy `std::input_iterator`, the re
[libcxx][nfc] prefixes test type `input_iterator` with `cpp17_`C++20 revised the definition of what it means to be an iterator. Whileall _Cpp17InputIterators_ satisfy `std::input_iterator`, the reverseisn't true. D100271 introduces a new test adaptor to accommodate thisnew definition (`cpp20_input_iterator`).In order to help readers immediately distinguish which input iteratoradaptor is _Cpp17InputIterator_, the current `input_iterator` adaptorhas been prefixed with `cpp17_`.Differential Revision: https://reviews.llvm.org/D101242
[libc++] Disable some tests using gcc 9.This should fix running the libc++ unit tests.They failed due to the changes introduced in 67c88e.
[libc++] P1645 constexpr for <numeric>Implements P1645: constexpr for <numeric> algorithmsReviewed By: ldionne, #libcDifferential Revision: https://reviews.llvm.org/D90569
[libc++] Use std::move in numeric algorithms (P0616R0).This patch updates algorithms in <numeric> to use std::movebased on p0616r0. Moving values instead of copying themcreates huge speed improve
[libc++] Use std::move in numeric algorithms (P0616R0).This patch updates algorithms in <numeric> to use std::movebased on p0616r0. Moving values instead of copying themcreates huge speed improvements (see the paper for details).Differential Revision: https://reviews.llvm.org/D61170
Revert "[libc++] P1645 constexpr for <numeric>"This reverts commit eb9b063539c34d0d4dd14e8516eeb77bb8b9e4bd.The commit fails to build on build bots using LLVM 8.
Add include for 'test_macros.h' to all the tests that were missing them. Thanks to Zoe for the (big, but simple) patch. NFC intended.llvm-svn: 362252
Support tests in freestandingSummary:Freestanding is *weird*. The standard allows it to differ in a bunch of oddmanners from regular C++, and the committee would like to improve thatsituation. I
Support tests in freestandingSummary:Freestanding is *weird*. The standard allows it to differ in a bunch of oddmanners from regular C++, and the committee would like to improve thatsituation. I'd like to make libc++ behave better with what freestanding shouldbe, so that it can be a tool we use in improving the standard. To do that weneed 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, usingclang 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" propertyhas 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'tcreate 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 justfalls of the end and does whatever undefined behavior (if you're luck, ud2leading to non-zero return code).Let's start my work with the basics. This patch changes all libc++ tests todeclare `main` as `int main(int, char**` so it mangles consistently (enabling usto declare another `extern "C"` main for freestanding which calls the mangledone), and adds `return 0;` to all places where it was missing. This touches 6124files, 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/793819ff360baa845483dde81170feedThis 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 filesystemtests), etc.Once this is in we can create a freestanding bot which will prevent furtherregressions. After that, we can start the real work of supporting C++freestanding fairly well in libc++.<rdar://problem/47754795>Reviewers: ldionne, mclow.lists, EricWFSubscribers: christof, jkorous, dexonsmith, arphaman, miyuki, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D57624llvm-svn: 353086
Update more file headers across all of the LLVM projects in the monorepoto reflect the new license. These used slightly different spellings thatdefeated my regular expressions.We understand that
Update more file headers across all of the LLVM projects in the monorepoto reflect the new license. These used slightly different spellings thatdefeated my regular expressions.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351648
Move test into test/std subdirectory.llvm-svn: 224658