<?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 __debug</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2aea8af2 - [libc++] Make _LIBCPP_DEBUG_RANDOMIZE_RANGE a function</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#2aea8af2</link>
        <description>[libc++] Make _LIBCPP_DEBUG_RANDOMIZE_RANGE a functionReviewed By: ldionne, Mordante, var-const, #libcSpies: mgorny, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D128181

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Sun, 03 Jul 2022 14:52:22 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>23d6cde1 - [libc++] Add a test to pin down the set of transitive public includes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#23d6cde1</link>
        <description>[libc++] Add a test to pin down the set of transitive public includesA situation that happens fairly often in libc++ is that we remove sometransitive includes in a header (either purposefully or not) and thatends up breaking users. Of course, we want to be able to remove ourtransitive includes, however it&apos;s also good to have a grip on thatto know which commit changed what and when. Furthermore, it&apos;s goodto accumulate include removals for a couple of releases to avoidbreaking users at every release for this reason.This commit adds a test that should break whenever we remove aninclude. Hence, it should allow us to track which headers includewhich other headers transitively, giving us a traceable way toremove headers.Differential Revision: https://reviews.llvm.org/D128236

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Mon, 20 Jun 2022 21:10:53 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f3966eaf - [libc++] Make the Debug mode a configuration-time only option</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#f3966eaf</link>
        <description>[libc++] Make the Debug mode a configuration-time only optionThe debug mode has been broken pretty much ever since it was shippedbecause it was possible to enable the debug mode in user code withoutactually enabling it in the dylib, leading to ODR violations thatcaused various kinds of failures.This commit makes the debug mode a knob that is configured whenbuilding the library and which can&apos;t be changed afterwards. This isless flexible for users, however it will actually work as intendedand it will allow us, in the future, to add various kinds of checksthat do not assume the same ABI as the normal library. Furthermore,this will make the debug mode more robust, which means that vendorsmight be more tempted to support it properly, which hasn&apos;t been thecase with the current debug mode.This patch shouldn&apos;t break any user code, except folks who are buildingagainst a library that doesn&apos;t have the debug mode enabled and who tryto enable the debug mode in their code. Such users will get a compile-timeerror explaining that this configuration isn&apos;t supported anymore.In the future, we should further increase the granularity of the debugmode checks so that we can cherry-pick which checks to enable, like wedo for unspecified behavior randomization.Differential Revision: https://reviews.llvm.org/D122941

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Fri, 01 Apr 2022 20:38:30 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>08f68dfe - [libc++] Add a few more debug wrapper functions</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#08f68dfe</link>
        <description>[libc++] Add a few more debug wrapper functionsReviewed By: ldionne, #libc, jloserSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D125176

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Sat, 07 May 2022 20:20:23 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>e70533ae - [libc++] Remove unused &lt;iosfwd&gt; include from &lt;__debug&gt;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#e70533ae</link>
        <description>[libc++] Remove unused &lt;iosfwd&gt; include from &lt;__debug&gt;Differential Revision: https://reviews.llvm.org/D122999

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Sun, 03 Apr 2022 16:40:39 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>cc82a1b0 - [libc++][NFC] Fix include guards and add a missing license header</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#cc82a1b0</link>
        <description>[libc++][NFC] Fix include guards and add a missing license header

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Wed, 23 Mar 2022 17:11:04 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f86c2b6f - [libc++] Add `explicit` to a bunch of internal detail ctors.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#f86c2b6f</link>
        <description>[libc++] Add `explicit` to a bunch of internal detail ctors.Notably the following ctors remain non-explicit because theyare used as implicit conversions in too many places:* __debug_less(_Compare&amp;)* __map_iterator(_TreeIterator)* __map_const_iterator(_TreeIterator)* __hash_map_iterator(_HashIterator)* __hash_map_const_iterator(_HashIterator)Differential Revision: https://reviews.llvm.org/D119894

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Wed, 09 Feb 2022 22:30:46 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>318507ed - [libc++] Remove a few unneeded _LIBCPP_CXX03_LANG ifdefs</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#318507ed</link>
        <description>[libc++] Remove a few unneeded _LIBCPP_CXX03_LANG ifdefsReviewed By: Quuxplusone, ldionne, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D119896

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Wed, 16 Feb 2022 17:55:43 +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/__debug#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/__debug</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>506cf6dc - [libc++] Fix modules and benchmarks CI builds when incomplete features are disabled</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#506cf6dc</link>
        <description>[libc++] Fix modules and benchmarks CI builds when incomplete features are disabledDifferential Revision: https://reviews.llvm.org/D119036

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Fri, 04 Feb 2022 20:37:01 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>157bbe6a - [libc++] Remove the ability to use the std::nullptr_t emulation in C++03 mode</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#157bbe6a</link>
        <description>[libc++] Remove the ability to use the std::nullptr_t emulation in C++03 modeBack in https://reviews.llvm.org/D109459, we stopped using the C++03emulation for std::nullptr_t by default, which was an ABI break. Westill left a knob for users to turn it back on if they were broken bythe change, with a note that we would remove that knob after one release.The time has now come to remove the knob and clean up the std::nullptr_temulation.Differential Revision: https://reviews.llvm.org/D114786

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Wed, 08 Sep 2021 16:57:58 +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/__debug#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/__debug</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>caf5548c - [libc++] Introduce __debug_db_insert_i()</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#caf5548c</link>
        <description>[libc++] Introduce __debug_db_insert_i()Introduce `__debug_db_insert_i()`Reviewed By: ldionne, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D117410

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Mon, 17 Jan 2022 18:25:21 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>42185ad8 - [libc++] Add tests verifying alphabetical order for several things.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#42185ad8</link>
        <description>[libc++] Add tests verifying alphabetical order for several things.These things are header #includes, CMakeLists.txt, and module.modulemap.Differential Revision: https://reviews.llvm.org/D116958

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</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>e3cf7050 - [libc++] Introduce __debug_db_insert_c()</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#e3cf7050</link>
        <description>[libc++] Introduce __debug_db_insert_c()There are a lot of```#if _LIBCPP_DEBUG_LEVEL == 2    __get_db()-&gt;__insert_c(this);#endif```This patch introduces `__debug_db_insert_c()` to put the `#if` in one central place.Reviewed By: ldionne, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D116947

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Mon, 10 Jan 2022 23:33:35 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>5675b611 - [libc++] Disable _LIBCPP_DEBUG_ASSERT during constant evaluation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#5675b611</link>
        <description>[libc++] Disable _LIBCPP_DEBUG_ASSERT during constant evaluationDisable `_LIBCPP_DEBUG_ASSERT` and debug iterators in &lt;string&gt; during constant evaluationReviewed By: ldionne, #libcSpies: goncharov, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D115788

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Thu, 16 Dec 2021 13:55:03 +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/__debug#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/__debug</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>4cd6ca10 - [libc++] NFC: Normalize `#endif //` comment indentation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#4cd6ca10</link>
        <description>[libc++] NFC: Normalize `#endif //` comment indentation

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</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>be4c657b - [libc++] Consistently replace `::new(__p) T` with `::new ((void*)__p) T`. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#be4c657b</link>
        <description>[libc++] Consistently replace `::new(__p) T` with `::new ((void*)__p) T`. NFCI.Everywhere, normalize the whitespace to `::new (EXPR) T`.Everywhere, normalize the spelling of the cast to `(void*)EXPR`.Without the cast to `(void*)`, the expression triggers ADL on GCC.(I think this is a GCC bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98249)Even if it doesn&apos;t trigger ADL, it still seems incorrect to use any argumentthat&apos;s not exactly `(void*)` because that opens the possibility of overloadresolution picking a user-defined overload of `operator new`, which would bewrong.Differential Revision: https://reviews.llvm.org/D93153

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Sat, 12 Dec 2020 01:30:28 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d586f92c - [libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__debug#d586f92c</link>
        <description>[libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.I used a lot of `git grep` to find places where `std::` was being usedoutside of comments and assert-messages. There were three outcomes:- Qualified function calls, e.g. `std::move` becomes `_VSTD::move`.    This is the most common case.- Typenames that don&apos;t need qualification, e.g. `std::allocator` becomes `allocator`.    Leaving these as `_VSTD::allocator` would also be fine, but I decided    that removing the qualification is more consistent with existing practice.- Names that specifically need un-versioned `std::` qualification,    or that I wasn&apos;t sure about. For example, I didn&apos;t touch any code in    &lt;atomic&gt;, &lt;math.h&gt;, &lt;new&gt;, or any ext/ or experimental/ headers;    and I didn&apos;t touch any instances of `std::type_info`.In some deduction guides, we were accidentally using `class Alloc = typename std::allocator&lt;T&gt;`,despite `std::allocator&lt;T&gt;`&apos;s type-ness not being template-dependent.Because `std::allocator` is a qualified name, this did parse as we intended;but what we meant was simply `class Alloc = allocator&lt;T&gt;`.Differential Revision: https://reviews.llvm.org/D92250

            List of files:
            /llvm-project-15.0.7/libcxx/include/__debug</description>
        <pubDate>Fri, 27 Nov 2020 16:02:06 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
