<?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 memory_resource</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><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/experimental/memory_resource#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/experimental/memory_resource</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>1458458b - [libc++] Remove &lt;utility&gt; includes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#1458458b</link>
        <description>[libc++] Remove &lt;utility&gt; includesReviewed By: ldionne, Quuxplusone, #libcSpies: libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D121054

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Mon, 07 Mar 2022 15:31:33 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>52915d78 - [libc++] Granularize &lt;utility&gt; includes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#52915d78</link>
        <description>[libc++] Granularize &lt;utility&gt; includesReviewed By: ldionne, #libcSpies: EricWF, libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D120466

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Sat, 05 Mar 2022 18:17:07 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>f87aa19b - [libc++] Move everything related solely to _LIBCPP_ASSERT to its own file</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#f87aa19b</link>
        <description>[libc++] Move everything related solely to _LIBCPP_ASSERT to its own fileThis is the first step towards disentangling the debug mode and assertionsin libc++. This patch doesn&apos;t make any functional change: it simply moves_LIBCPP_ASSERT-related stuff to its own file so as to make it clear thatlibc++ assertions and the debug mode are different things. Future patcheswill make it possible to enable assertions without enabling the debugmode.Differential Revision: https://reviews.llvm.org/D119769

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Mon, 14 Feb 2022 18:41:09 +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/experimental/memory_resource#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/experimental/memory_resource</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>4d81a46f - [libc++] Alphabetize header #includes. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#4d81a46f</link>
        <description>[libc++] Alphabetize header #includes. NFCI.The NFC part of D116809. We still want to enforce this in CI,but the mechanism for that is still to-be-determined.Differential Revision: https://reviews.llvm.org/D116809

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Fri, 07 Jan 2022 14:45:05 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&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/experimental/memory_resource#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/experimental/memory_resource</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/experimental/memory_resource#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/experimental/memory_resource</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>0a20660c - [libcxx] Resolve LWG 2724 protected -&gt; private.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#0a20660c</link>
        <description>[libcxx] Resolve LWG 2724 protected -&gt; private.Fixes LWG issue 2724: &quot;The protected virtual member functions of memory_resource should be private.&quot;Differential Revision: https://reviews.llvm.org/D66615

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Mon, 23 Nov 2020 22:21:50 +0000</pubDate>
        <dc:creator>zoecarver &lt;z.zoelec2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b66754a2 - Revert &quot;[coroutines] Add std::experimental::task&lt;T&gt; type&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#b66754a2</link>
        <description>Revert &quot;[coroutines] Add std::experimental::task&lt;T&gt; type&quot;This revision is causing build and test failures, such ashttp://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-armv8-linux/builds/648/steps/test.libcxx/logs/stdio,so I&apos;ll revert it.llvm-svn: 357023

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Tue, 26 Mar 2019 19:50:46 +0000</pubDate>
        <dc:creator>Brian Gesiak &lt;modocache@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>57839425 - [coroutines] Add std::experimental::task&lt;T&gt; type</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#57839425</link>
        <description>[coroutines] Add std::experimental::task&lt;T&gt; typeSummary:Adds the coroutine `std::experimental::task&lt;T&gt;` type described in proposal P1056R0.See https://wg21.link/P1056R0.This implementation allows customization of the allocator used to allocate thecoroutine frame by passing std::allocator_arg as the first argument, followed bythe allocator to use.This supports co_awaiting the same task multiple times. The second andsubsequent times it returns a reference to the already-computed value.This diff also adds some implementations of other utilities that have potential forstandardization as helpers within the test/... area:- `sync_wait(awaitable)` - See P1171R0- `manual_reset_event`Move the definition of the __aligned_allocation_size helper functionfrom &lt;experimental/memory_resource&gt; to &lt;experimental/__memory&gt;so it can be more widely used without pulling in memory_resource.Outstanding work:- Use C++14 keywords directly rather than macro versions  eg. use `noexcept` instead of `_NOEXCEPT`).- Add support for overaligned coroutine frames.  This may need wording in the Coroutines TS to support passing the extra `std::align_val_t`.- Eliminate use of `if constexpr` if we want it to compile under C++14.Patch by @lewissbaker (Lewis Baker).llvm-svn: 357010

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Tue, 26 Mar 2019 17:46:06 +0000</pubDate>
        <dc:creator>Brian Gesiak &lt;modocache@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2946cd70 - Update the file headers across all of the LLVM projects in the monorepo</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#2946cd70</link>
        <description>Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we&apos;re moving the headerentirely to discuss the new license. We checked this carefully with theFoundation&apos;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: 351636

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Sat, 19 Jan 2019 08:50:56 +0000</pubDate>
        <dc:creator>Chandler Carruth &lt;chandlerc@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d108bf85 - Move internal usages of `alignof`/`__alignof` to use `_LIBCPP_ALIGNOF`. </title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#d108bf85</link>
        <description>Move internal usages of `alignof`/`__alignof` to use `_LIBCPP_ALIGNOF`. Summary:Starting in Clang 8.0 and GCC 8.0, `alignof` and `__alignof` return different values in same cases. Specifically `alignof` and `_Alignof` return the minimum alignment for a type, where as `__alignof` returns the preferred alignment. libc++ currently uses `__alignof` but means to use `alignof`. See  llvm.org/PR39713This patch introduces the macro `_LIBCPP_ALIGNOF` so we can control which spelling gets used.This patch does not introduce any ABI guard to provide the old behavior with newer compilers. However, if we decide that is needed, this patch makes it trivial to implement.I think we should commit this change immediately, and decide what we want to do about the ABI afterwards. Reviewers: ldionne, EricWFReviewed By: ldionne, EricWFSubscribers: jyknight, christof, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D54814llvm-svn: 351289

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Wed, 16 Jan 2019 01:51:12 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>cb5b004a - Remove unused code from __functional_base. NFC.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#cb5b004a</link>
        <description>Remove unused code from __functional_base. NFC.Patch from Arthur O&apos;Dwyer.`__user_alloc_construct_impl` is used by &lt;experimental/memory_resource&gt;, butthis `__user_alloc_construct` is never used.Also, `&lt;experimental/memory_resource&gt;` doesn&apos;t need a full definition of`std::tuple`; just the forward declaration in `&lt;__tuple&gt;` will suffice.Reviewed as https://reviews.llvm.org/D46806llvm-svn: 334069

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Wed, 06 Jun 2018 06:42:27 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>bd2e9498 - LWG 2969 &quot;polymorphic_allocator::construct() shouldn&apos;t pass resource()&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#bd2e9498</link>
        <description>LWG 2969 &quot;polymorphic_allocator::construct() shouldn&apos;t pass resource()&quot;Patch from Arthur O&apos;Dwyer.In the TS, `uses_allocator` construction for `pair` tried to use an allocatortype of `memory_resource*`, which is incorrect because `memory_resource*` isnot an allocator type. LWG 2969 fixed it to use `polymorphic_allocator` as theallocator type instead.https://wg21.link/lwg2969(D47090 included this in `&lt;memory_resource&gt;`; at Eric&apos;s request, I&apos;ve splitthis out into its own patch applied to the existing`&lt;experimental/memory_resource&gt;` instead.)Reviewed as https://reviews.llvm.org/D47109llvm-svn: 333384

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Tue, 29 May 2018 00:08:47 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>a016efb1 - [Libc++] Use #pragma push_macro/pop_macro to better handle min/max on Windows</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#a016efb1</link>
        <description>[Libc++] Use #pragma push_macro/pop_macro to better handle min/max on WindowsSummary:This patch improves how libc++ handles min/max macros within the headers. Previously libc++ would undef them and emit a warning.This patch changes libc++ to use `#pragma push_macro`  to save the macro before undefining it, and `#pragma pop_macro` to restore the macros and the end of the header.Reviewers: mclow.lists, bcraig, compnerd, EricWFReviewed By: EricWFSubscribers: cfe-commits, krytarowskiDifferential Revision: https://reviews.llvm.org/D33080llvm-svn: 304357

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Wed, 31 May 2017 22:07:49 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>25f9f927 - remove max_size() extension from polymorphic_allocator. It is unneeded</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#25f9f927</link>
        <description>remove max_size() extension from polymorphic_allocator. It is unneededllvm-svn: 296831

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Thu, 02 Mar 2017 22:10:14 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>e2f2d1ed - [NFC] Rename _LIBCPP_TYPE_VIS_ONLY to _LIBCPP_TEMPLATE_VIS</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#e2f2d1ed</link>
        <description>[NFC] Rename _LIBCPP_TYPE_VIS_ONLY to _LIBCPP_TEMPLATE_VISThe name _LIBCPP_TYPE_VIS_ONLY is no longer accurate because both_LIBCPP_TYPE_VIS and _LIBCPP_TYPE_VIS_ONLY expand to__attribute__((__type_visibility__)) with Clang. The only remaining differenceis that _LIBCPP_TYPE_VIS_ONLY can be applied to templates whereas_LIBCPP_TYPE_VIS cannot (due to dllimport/dllexport not being allowed ontemplates).This patch renames _LIBCPP_TYPE_VIS_ONLY to _LIBCPP_TEMPLATE_VIS.llvm-svn: 291035

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Wed, 04 Jan 2017 23:56:00 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>0fc8cec7 - Followon to r279744. Find the other exception types and make __throw_XXX routines (and call them).  Remove the generic __libcpp_throw routine, since no one uses it anymore.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#0fc8cec7</link>
        <description>Followon to r279744. Find the other exception types and make __throw_XXX routines (and call them).  Remove the generic __libcpp_throw routine, since no one uses it anymore.llvm-svn: 279763

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Thu, 25 Aug 2016 17:47:09 +0000</pubDate>
        <dc:creator>Marshall Clow &lt;mclow.lists@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8b7faa68 - Implement p0337r0. Delete operator= for polymorphic_allocator.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/experimental/memory_resource#8b7faa68</link>
        <description>Implement p0337r0. Delete operator= for polymorphic_allocator.llvm-svn: 273838

            List of files:
            /llvm-project-15.0.7/libcxx/include/experimental/memory_resource</description>
        <pubDate>Mon, 27 Jun 2016 00:55:25 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
</channel>
</rss>
