Changes in destroy_at.pass.cpp

b9bc3c10 - [libc++][ranges] Implement `construct_at` and `destroy{,_at}`.

Thu, 13 Jan 2022 00:00:44 +0000

[libc++][ranges] Implement `construct_at` and `destroy{,_at}`.Differential Revision: https://reviews.llvm.org/D116078 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

5425106e - [libc++] Remove test-suite annotations for unsupported Clang versions

Fri, 20 Aug 2021 15:42:38 +0000

[libc++] Remove test-suite annotations for unsupported Clang versionsDifferential Revision: https://reviews.llvm.org/D108471 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

6900df37 - [libc++] Remove Lit annotations for unsupported GCC versions from the test suite

Mon, 09 Aug 2021 22:08:39 +0000

[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 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

c99f5b2a - [libc++] Handle arrays in std::destroy_at

Tue, 27 Jul 2021 19:45:09 +0000

[libc++] Handle arrays in std::destroy_atAlso, improve tests for std::destroy and std::destroy_n so that theycheck for array support.These changes are part of http://wg21.link/p0896 (the One Ranges proposal).Differential Revision: https://reviews.llvm.org/D106916 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

5641b1df - [libc++] Mark a few more tests as unsupported on gcc-8/9.

Thu, 26 Nov 2020 11:40:50 +0000

[libc++] Mark a few more tests as unsupported on gcc-8/9.This will fix remaining failures on gcc-9 buildbot: http://lab.llvm.org:8011/#/builders/101.gcc-8 and gcc-9 do not support constexpr destructors nor constexpr allocation.Fix gcc warnings: -Wconversion, -Wpragmas. List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

8041f13e - [libc++] Skip tests using constexpr destructors with older clang versions

Mon, 19 Oct 2020 16:22:54 +0000

[libc++] Skip tests using constexpr destructors with older clang versionsIt appears that the released version of clang that supports constexprdestructors is clang 10 and the oldest one that accepts -std=c++2a is 5,so mark these as UNSUPPORTED for clang-5 to clang-9.Reviewed By: #libc, ldionneDifferential Revision: https://reviews.llvm.org/D89704 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

d092c912 - [libc++] Fix constexpr dynamic allocation on GCC 10

Mon, 28 Sep 2020 21:29:52 +0000

[libc++] Fix constexpr dynamic allocation on GCC 10We're technically not allowed by the Standard to call ::operator new inconstexpr functions like __libcpp_allocate. Clang doesn't seem to complainabout it, but GCC does. List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

0724f8bf - [libc++] Implement C++20's P0784 (More constexpr containers)

Thu, 17 Sep 2020 16:06:13 +0000

[libc++] Implement C++20's P0784 (More constexpr containers)This commit adds std::construct_at, and marks various members ofstd::allocator_traits and std::allocator as constexpr. It also addstests and turns the existing tests into hybrid constexpr/runtime tests.Thanks to Richard Smith for initial work on this, and to Michael Parkfor D69803, D69132 and D69134, which are superseded by this patch.Differential Revision: https://reviews.llvm.org/D68364 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.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/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

7fc6a556 - 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.

Fri, 31 May 2019 18:35:30 +0000

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 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.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/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.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/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

2e99ae4f - Fix memory leak in test.

Sun, 24 Jul 2016 04:41:44 +0000

Fix memory leak in test.llvm-svn: 276547 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp

e4d9c316 - Implement P0040r3: Extending memory management tools

Sun, 24 Jul 2016 03:51:39 +0000

Implement P0040r3: Extending memory management toolsllvm-svn: 276544 List of files: /llvm-project-15.0.7/libcxx/test/std/utilities/memory/specialized.algorithms/specialized.destroy/destroy_at.pass.cpp