<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in new</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>56a33ba3 - [libc++] Implement P0154R1 (Hardware inference size)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#56a33ba3</link>
        <description>[libc++] Implement P0154R1 (Hardware inference size)`__GCC_CONSTRUCTIVE_SIZE` and `__GCC_DESTRUCTIVE_SIZE` are available since GCC 12. I&apos;m assuming clang will also implement these for compatability with libstdc++.Reviewed By: ldionne, #libcSpies: h-vetinari, libcxx-commits, arichardsonDifferential Revision: https://reviews.llvm.org/D122276

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 22 Jun 2022 19:10:57 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>385cc25a - [libc++] Ensure that all public C++ headers include &lt;__assert&gt;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#385cc25a</link>
        <description>[libc++] Ensure that all public C++ headers include &lt;__assert&gt;This patch changes the requirement for getting the declaration of theassertion handler from including &lt;__assert&gt; to including any publicC++ header of the library. Note that C compatibility headers areexcluded because we don&apos;t implement all the C headers ourselves --some of them are taken straight from the C library, like assert.h.It also adds a generated test to check it. Furthermore, this newgenerated test is designed in a way that will make it possible toreplace almost all the existing test-generation scripts with thissystem in upcoming patches.Differential Revision: https://reviews.llvm.org/D122506

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Fri, 25 Mar 2022 16:55:36 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>fa6b9e40 - [libc++] Normalize all our &apos;#pragma GCC system_header&apos;, and regression-test.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#fa6b9e40</link>
        <description>[libc++] Normalize all our &apos;#pragma GCC system_header&apos;, and regression-test.Now we&apos;ll notice if a header forgets to include this magic phrase.Differential Revision: https://reviews.llvm.org/D118800

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 02 Feb 2022 01:16:40 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d2b0df35 - [libc++][NFC] Update namespace comments in include/</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#d2b0df35</link>
        <description>[libc++][NFC] Update namespace comments in include/update the namspace comments in include/Reviewed By: ldionne, #libcSpies: smeenai, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D114947

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Thu, 02 Dec 2021 13:12:51 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>eb8650a7 - [runtimes][NFC] Remove filenames at the top of the license notice</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#eb8650a7</link>
        <description>[runtimes][NFC] Remove filenames at the top of the license noticeWe&apos;ve stopped doing it in libc++ for a while now because these nameswould end up rotting as we move things around and copy/paste stuff.This cleans up all the existing files so as to stop the spreadingas people copy-paste headers around.

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 17 Nov 2021 21:25:01 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>be10b1f1 - [libcxx] Make allocator&lt;T&gt;:allocate throw bad_array_new_length</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#be10b1f1</link>
        <description>[libcxx] Make allocator&lt;T&gt;:allocate throw bad_array_new_lengthCurrently the member functions std::allocator&lt;T&gt;::allocate,std::experimental::pmr::polymorphic_allocator::allocate andstd::resource_adaptor&lt;T&gt;::do_allocate throw an exception of typestd::length_error when the requested size exceeds the maximum size.According to the C++ standard ([allocator.members]/4,[mem.poly.allocator.mem]/1), std::allocator&lt;T&gt;::allocate andstd::pmr::polymorphic_allocator::allocate must throw astd::bad_array_new_length exception in this case.The patch fixes the issue with std::allocator&lt;T&gt;::allocate and changesthe type the exception thrown bystd::experimental::pmr::resource_adaptor&lt;T&gt;::do_allocate tostd::bad_array_new_length as well for consistency.The patch resolves LWG 3237, LWG 3038 and LWG 3190.Reviewed By: ldionne, #libc, QuuxplusoneDifferential Revision: https://reviews.llvm.org/D110846

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Mon, 18 Oct 2021 18:12:42 +0000</pubDate>
        <dc:creator>Mikhail Maltsev &lt;mikhail.maltsev@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>cb793e1a - [libc++][NFCI] Remove uses of _LIBCPP_INLINE_VAR</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#cb793e1a</link>
        <description>[libc++][NFCI] Remove uses of _LIBCPP_INLINE_VARAll supported compilers provide support for inline variables in C++17 now.Also, as a fly-by fix, replace some uses of _LIBCPP_CONSTEXPR by justconstexpr.The only exception in this patch is `std::ignore`, which is providedprior to C++17. Since it is defined in an anonymous namespace, it alwayshas internal linkage anyway, so using an inline variable there doesn&apos;tprovide any benefit. Instead, `inline` was removed entirely on `std::ignore`.Differential Revision: https://reviews.llvm.org/D110243

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 22 Sep 2021 13:35:32 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a4cb5aef - [libc++] Remove some workarounds for unsupported GCC and Clang versions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#a4cb5aef</link>
        <description>[libc++] Remove some workarounds for unsupported GCC and Clang versionsThere is a lot more we can do, in particular in &lt;type_traits&gt;, but thisremoves some workarounds that were gated on checking a specific compilerversion.Differential Revision: https://reviews.llvm.org/D108923

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Tue, 31 Aug 2021 14:49:06 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e79474d3 - [libc++][NFC] Add missing HIDE_FROM_ABI on implementation detail __launder</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#e79474d3</link>
        <description>[libc++][NFC] Add missing HIDE_FROM_ABI on implementation detail __launder

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Tue, 31 Aug 2021 14:29:22 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>bfbd73f8 - [libc++] Alphabetize and include-what-you-use. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#bfbd73f8</link>
        <description>[libc++] Alphabetize and include-what-you-use. NFCI.Differential Revision: https://reviews.llvm.org/D102781

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 19 May 2021 15:57:04 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>4cd6ca10 - [libc++] NFC: Normalize `#endif //` comment indentation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#4cd6ca10</link>
        <description>[libc++] NFC: Normalize `#endif //` comment indentation

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Tue, 20 Apr 2021 16:03:32 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>3744ba24 - [NFC][libc++] Suppress &quot;warning: ignoring return value&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#3744ba24</link>
        <description>[NFC][libc++] Suppress &quot;warning: ignoring return value&quot;According to the comment on the next lineit&apos;s expected behaviour.

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Fri, 26 Feb 2021 22:29:06 +0000</pubDate>
        <dc:creator>Vitaly Buka &lt;vitalybuka@google.com&gt;</dc:creator>
    </item>
<item>
        <title>044b892c - [libc++] Use c++20 instead of c++2a consistently.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#044b892c</link>
        <description>[libc++] Use c++20 instead of c++2a consistently.* The only exception is that the flag -std=c++2a is still used not to break compatibility with older compilers (clang &lt;= 9, gcc &lt;= 9).* Bump _LIBCPP_STD_VER for C++20 to 20 and use 21 for the future standard (C++2b).That&apos;s a preparation step to add c++2b support to libc++.Reviewed By: ldionne, #libcDifferential Revision: https://reviews.llvm.org/D93383

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Thu, 07 Jan 2021 11:29:04 +0000</pubDate>
        <dc:creator>Marek Kurdej &lt;marek.kurdej@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a78aaa1a - [libc++] Factor out common logic for calling aligned allocation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#a78aaa1a</link>
        <description>[libc++] Factor out common logic for calling aligned allocationThere were a couple of places where we needed to call the underlyingplatform&apos;s aligned allocation/deallocation function. Instead of havingthe same logic all over the place, extract the logic into a pair ofhelper functions __libcpp_aligned_alloc and __libcpp_aligned_free.The code in libcxxabi/src/fallback_malloc.cpp looks like it could besimplified after this change -- I purposefully did not simplify itfurther to keep this change as straightforward as possible, since itis touching very important parts of the library.Also, the changes in libcxx/src/new.cpp and libcxxabi/src/stdlib_new_delete.cppare basically the same -- I just kept both source files in sync.The underlying reason for this refactoring is to make it easier to supportplatforms that provide aligned allocation through C11&apos;s aligned_allocfunction instead of posix_memalign. After this change, we&apos;ll only haveto add support for that in a single place.Differential Revision: https://reviews.llvm.org/D91379

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Thu, 12 Nov 2020 20:14:33 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>2eadbc86 - [libc++] Rework the whole availability markup implementation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#2eadbc86</link>
        <description>[libc++] Rework the whole availability markup implementationCurrently, vendor-specific availability markup is enabled by default.This means that even when building against trunk libc++, the headerswill by default prevent you from using some features that were notreleased in the dylib on your target platform. This is a source offrustration since people building libc++ from sources are usually nottrying to use some vendor&apos;s released dylib.For that reason, I&apos;ve been thinking for a long time that availabilityannotations should be off by default, which is the primary change thatthis commit enables.In addition, it reworks the implementation to make it easier for newvendors to add availability annotations for their platform, and itrefreshes the documentation to reflect the current state of the codebase.Finally, a CMake configuration option is added to control whetheravailability annotations should be turned on for the flavor of libc++being created. The intent is for vendors like Apple to turn it on, andfor the upstream libc++ to leave it off (the default).Differential Revision: https://reviews.llvm.org/D90843

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Wed, 04 Nov 2020 20:01:25 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>c778f6c4 - [libc++] Clean up logic around aligned/sized allocation and deallocation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#c778f6c4</link>
        <description>[libc++] Clean up logic around aligned/sized allocation and deallocationDue to the need to support compilers that implement builtin operatornew/delete but not their align_val_t overloaded versions, there was alot of complexity. By assuming that a compiler that supports the builtinnew/delete operators also supports their align_val_t overloads, the codecan be simplified quite a bit.Differential Revision: https://reviews.llvm.org/D88301

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Fri, 25 Sep 2020 13:24:14 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>d092c912 - [libc++] Fix constexpr dynamic allocation on GCC 10</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#d092c912</link>
        <description>[libc++] Fix constexpr dynamic allocation on GCC 10We&apos;re technically not allowed by the Standard to call ::operator new inconstexpr functions like __libcpp_allocate. Clang doesn&apos;t seem to complainabout it, but GCC does.

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Mon, 28 Sep 2020 21:29:52 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>0724f8bf - [libc++] Implement C++20&apos;s P0784 (More constexpr containers)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#0724f8bf</link>
        <description>[libc++] Implement C++20&apos;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/include/new</description>
        <pubDate>Thu, 17 Sep 2020 16:06:13 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>7c2f4a83 - [libc++] Revert 03dd205c151 &quot;Adjust max_align_t handling&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#7c2f4a83</link>
        <description>[libc++] Revert 03dd205c151 &quot;Adjust max_align_t handling&quot;That commit was made without approval from a libc++ reviewer, and italso broke the build in C++03 mode.

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Tue, 25 Feb 2020 16:42:08 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>03dd205c - Adjust max_align_t handling</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/new#03dd205c</link>
        <description>Adjust max_align_t handlingDepend on the compiler to provide a correct implementation ofmax_align_t. If __STDCPP_NEW_ALIGNMENT__ is missing and C++03 mode hasbeen explicitly enabled, provide a minimal fallback in &lt;new&gt; asalignment of the largest primitive types.

            List of files:
            /llvm-project-15.0.7/libcxx/include/new</description>
        <pubDate>Tue, 04 Feb 2020 14:04:42 +0000</pubDate>
        <dc:creator>Joerg Sonnenberger &lt;joerg@bec.de&gt;</dc:creator>
    </item>
</channel>
</rss>
