Changes in assign_copy.fail.cpp

a7f9895c - [runtimes] Rename various libcpp-has-no-XYZ Lit features to just no-XYZ

Thu, 26 May 2022 15:49:47 +0000

[runtimes] Rename various libcpp-has-no-XYZ Lit features to just no-XYZSince those features are general properties of the environment, it makessense to use them from libc++abi too, and so the name libcpp-has-no-xxxdoesn't make sense.Differential Revision: https://reviews.llvm.org/D126482 List of files: /llvm-project-15.0.7/libcxx/test/std/thread/futures/futures.task/futures.task.members/assign_copy.fail.cpp

31cbe0f2 - [libc++] Remove the c++98 Lit feature from the test suite

Mon, 01 Jun 2020 14:38:23 +0000

[libc++] Remove the c++98 Lit feature from the test suiteC++98 and C++03 are effectively aliases as far as Clang is concerned.As such, allowing both std=c++98 and std=c++03 as Lit parameters isjust slightly confusing, but provides no value. It's similar to allowingboth std=c++17 and std=c++1z, which we don't do.This was discovered because we had an internal bot that ran the testsuite under both c++98 AND c++03 -- one of which is redundant.Differential Revision: https://reviews.llvm.org/D80926 List of files: /llvm-project-15.0.7/libcxx/test/std/thread/futures/futures.task/futures.task.members/assign_copy.fail.cpp

2df59c50 - Support tests in freestanding

Mon, 04 Feb 2019 20:31:13 +0000

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++.Reviewers: ldionne, mclow.lists, EricWFSubscribers: christof, jkorous, dexonsmith, arphaman, miyuki, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D57624llvm-svn: 353086 List of files: /llvm-project-15.0.7/libcxx/test/std/thread/futures/futures.task/futures.task.members/assign_copy.fail.cpp

57b08b09 - Update more file headers across all of the LLVM projects in the monorepo

Sat, 19 Jan 2019 10:56:40 +0000

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 List of files: /llvm-project-15.0.7/libcxx/test/std/thread/futures/futures.task/futures.task.members/assign_copy.fail.cpp

eb5cfb02 - Cleanup non-standard tests as reported by STL@microsoft.com. NFC.

Wed, 01 Jun 2016 21:05:53 +0000

Cleanup non-standard tests as reported by STL@microsoft.com. NFC.This patch addresses the following issues in the test suite:1. Move "std::bad_array_length" test from std/ to libcxx/ test directory since the feature is not a part of the standard.2. Rename "futures.tas" test directory to "futures.task" since that is the correct stable name.3. Move tests for "packaged_task::result_type" from std/ to libcxx/ test directory since the typedef is a libc++ extension.llvm-svn: 271430 List of files: /llvm-project-15.0.7/libcxx/test/std/thread/futures/futures.task/futures.task.members/assign_copy.fail.cpp