<?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 __config</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a8af9f67 - Bump version to 15.0.7</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#a8af9f67</link>
        <description>Bump version to 15.0.7

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Fri, 06 Jan 2023 21:09:17 +0000</pubDate>
        <dc:creator>Tom Stellard &lt;tstellar@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>25a36ca5 - Bump version to 15.0.6</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#25a36ca5</link>
        <description>Bump version to 15.0.6

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 21 Nov 2022 18:38:24 +0000</pubDate>
        <dc:creator>Tom Stellard &lt;tstellar@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>154e88af - Bump version to 15.0.5</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#154e88af</link>
        <description>Bump version to 15.0.5

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Wed, 16 Nov 2022 06:28:29 +0000</pubDate>
        <dc:creator>Tom Stellard &lt;tstellar@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>5388da13 - Bump version to 15.0.4</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#5388da13</link>
        <description>Bump version to 15.0.4

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 24 Oct 2022 11:45:36 +0000</pubDate>
        <dc:creator>Tobias Hieta &lt;tobias@hieta.se&gt;</dc:creator>
    </item>
<item>
        <title>fc47af8c - Bump version to 15.0.3</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#fc47af8c</link>
        <description>Bump version to 15.0.3

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 10 Oct 2022 06:53:34 +0000</pubDate>
        <dc:creator>Tobias Hieta &lt;tobias@hieta.se&gt;</dc:creator>
    </item>
<item>
        <title>bcb9b9fc - [libcxx] Make stdatomic.h work when included from a C source file</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#bcb9b9fc</link>
        <description>[libcxx] Make stdatomic.h work when included from a C source fileIf a C source file includes the libc++ stdatomic.h, compilation willbreak because (a) the C++ standard check will fail (which is expected),and (b) `_LIBCPP_COMPILER_CLANG_BASED` won&apos;t be defined because thelogic defining it in `__config` is guarded by a `__cplusplus` check, sowe&apos;ll end up with a blank header. Move the detection logic outside ofthe `__cplusplus` check to make the second check pass even in a C contextwhen you&apos;re using Clang. Note that `_LIBCPP_STD_VER` is not defined whenin C mode, hence stdatomic.h needs to check if in C++ mode before usingthat macro to avoid a warning.In an ideal world, a C source file wouldn&apos;t be including the libc++header directory in its search path, so we&apos;d never have this issue.Unfortunately, certain build environments make this hard to guarantee,and in this case it&apos;s easy to tweak this header to make it work in a Ccontext, so I&apos;m hoping this is acceptable.Fixes https://github.com/llvm/llvm-project/issues/57710.Differential Revision: https://reviews.llvm.org/D134591(cherry picked from commit afec0f0ec38a72bcc6a697c1cefb1dac0bbd02fb)

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Tue, 27 Sep 2022 11:59:55 +0000</pubDate>
        <dc:creator>Gergely Nagy &lt;ngg@ngg.hu&gt;</dc:creator>
    </item>
<item>
        <title>451e3b68 - Bump version to 15.0.2</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#451e3b68</link>
        <description>Bump version to 15.0.2

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 26 Sep 2022 06:22:40 +0000</pubDate>
        <dc:creator>Tobias Hieta &lt;tobias@hieta.se&gt;</dc:creator>
    </item>
<item>
        <title>8d802f78 - [libc++] Keep unary_function and binary_function in C++17 for one more release</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#8d802f78</link>
        <description>[libc++] Keep unary_function and binary_function in C++17 for one more releaseIn LLVM 15, we added the deprecation markup for unary_function andbinary_function for &gt;= C++11, and we also removed it for &gt;= C++17.While this is in accordance with the Standard, it&apos;s also a bit quickfor our users, since there was no release in which the classes weremarked as deprecated before their removal.We noticed widespread breakage due to this, and after months of tryingto fix downstream failures, I am coming to the conclusion that userswill be better served if we give them one release where unary_functionis deprecated but still provided even in &gt;= C++17.Differential Revision: https://reviews.llvm.org/D134473

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 22 Sep 2022 20:17:31 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>43b5b04f - [libcxx] Bump libc++ version to 15.0.1</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#43b5b04f</link>
        <description>[libcxx] Bump libc++ version to 15.0.1

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 19 Sep 2022 17:47:45 +0000</pubDate>
        <dc:creator>Tobias Hieta &lt;tobias@hieta.se&gt;</dc:creator>
    </item>
<item>
        <title>deb3b555 - [libc++] Take advantage of -fexperimental-library in libc++</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#deb3b555</link>
        <description>[libc++] Take advantage of -fexperimental-library in libc++When -fexperimental-library is passed, libc++ will now pick up theappropriate __has_feature flag defined by Clang to enable theexperimental library features.As a fly-by, also update the documentation for the various TSes.Differential Revision: https://reviews.llvm.org/D130176

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Wed, 20 Jul 2022 14:42:04 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8711fcae - [libc++] Treat incomplete features just like other experimental features</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#8711fcae</link>
        <description>[libc++] Treat incomplete features just like other experimental featuresIn particular remove the ability to expel incomplete features from thelibrary at configure-time, since this can now be done through the_LIBCPP_ENABLE_EXPERIMENTAL macro.Also, never provide symbols related to incomplete features inside thedylib, instead provide them in c++experimental.a (this changes thesymbols list, but not for any configuration that should have shipped).Differential Revision: https://reviews.llvm.org/D128928

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 30 Jun 2022 15:57:52 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>64d63f48 - [libc++] Error if someone tries to use MSVC and tell them to contact the libc++ developers</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#64d63f48</link>
        <description>[libc++] Error if someone tries to use MSVC and tell them to contact the libc++ developersNobody knows if there are users of libc++ with MSVC. Let&apos;s try to find that out and encourage them to upstream their changes to make that configuration work.Reviewed By: ldionne, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D129055

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 04 Jul 2022 01:07:26 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>0f050528 - [libc++] Allow setting _LIBCPP_OVERRIDABLE_FUNC_VIS</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#0f050528</link>
        <description>[libc++] Allow setting _LIBCPP_OVERRIDABLE_FUNC_VISChromium changes this flag to be able to use a custom new/delete from adylib.

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 14 Jul 2022 13:04:36 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>d2e86866 - [libc++] Re-apply the use of ABI tags to provide per-TU insulation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#d2e86866</link>
        <description>[libc++] Re-apply the use of ABI tags to provide per-TU insulationThis commit re-applies 9ee97ce3b830, which was reverted by 61d417cebecause it broke the LLDB data formatter tests. It also re-applies6148c79a (the manual GN change associated to it).Differential Revision: https://reviews.llvm.org/D127444

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 07 Jul 2022 18:07:37 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>61d417ce - Revert &quot;[libc++] Use ABI tags instead of internal linkage to provide per-TU insulation&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#61d417ce</link>
        <description>Revert &quot;[libc++] Use ABI tags instead of internal linkage to provide per-TU insulation&quot;This reverts commit 9ee97ce3b8305c5762ec34eecb4daf379984c95b.

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 07 Jul 2022 15:48:21 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>9ee97ce3 - [libc++] Use ABI tags instead of internal linkage to provide per-TU insulation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#9ee97ce3</link>
        <description>[libc++] Use ABI tags instead of internal linkage to provide per-TU insulationInstead of marking private symbols with internal_linkage (which leads toone copy per translation unit -- rather wasteful), use an ABI tag thatgets rev&apos;d with each libc++ version. That way, we know that we can&apos;t havename collisions between implementation-detail functions across libc++versions, so we&apos;ll never violate the ODR. However, within a single program,each symbol still has a proper name with external linkage, which meansthat the linker is free to deduplicate symbols even across TUs.This actually means that we can guarantee that versions of libc++ canbe mixed within the same program without ever having to take a code sizehit, and without having to manually opt-in -- it should just work out ofthe box.Differential Revision: https://reviews.llvm.org/D127444

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Thu, 09 Jun 2022 21:36:33 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>633d1d0d - [libc++] Use bounded iterators in std::span when the debug mode is enabled</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#633d1d0d</link>
        <description>[libc++] Use bounded iterators in std::span when the debug mode is enabledPreviously, we&apos;d use raw pointers when the debug mode was enabled,which means we wouldn&apos;t get out-of-range checking with std::span&apos;siterators.This patch introduces a new class called __bounded_iter which canbe used to wrap iterators and make them carry around bounds-relatedinformation. This allows iterators to assert when they are dereferencedoutside of their bounds.As a fly-by change, this commit removes the _LIBCPP_ABI_SPAN_POINTER_ITERATORSknob. Indeed, not using a raw pointer as the iterator type is useful toavoid users depending on properties of raw pointers in their code.This is an alternative to D127401.Differential Revision: https://reviews.llvm.org/D127418

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Mon, 06 Jun 2022 18:01:38 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>60f7bdfd - [libc++][AIX] Make basic_string layout compatible with earlier version</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#60f7bdfd</link>
        <description>[libc++][AIX] Make basic_string layout compatible with earlier versionSummary:Patch D123580 changed to use bit fields for strings in long and short mode. As a result, this changes the layout of these strings on AIX because bit fields on AIX are 4 bytes, which breaks the ABI compatibility with earlier strings before the change on AIX. This patch uses the attribute &apos;packed&apos; and anonymous structure to make string layout compatible. This patch will also make test cases alignof.compile.pass.cpp and sizeof.compile.pass.cpp introduced in D127672 pass on AIX.Reviewed by: philnik, Mordante, hubert.reinterpretcast, libc++Differential Revision: https://reviews.llvm.org/D128285

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Fri, 24 Jun 2022 21:25:15 +0000</pubDate>
        <dc:creator>Xing Xue &lt;xingxue@outlook.com&gt;</dc:creator>
    </item>
<item>
        <title>758504b8 - [libc++] Simplify the visibility attributes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#758504b8</link>
        <description>[libc++] Simplify the visibility attributesReviewed By: ldionne, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D128007

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Wed, 22 Jun 2022 09:14:04 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>681cde7d - [libc++] Complete the implementation of N4190</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__config#681cde7d</link>
        <description>[libc++] Complete the implementation of N4190Fixes #37402Reviewed By: ldionneSpies: EricWF, avogelsgesang, libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D124346

            List of files:
            /llvm-project-15.0.7/libcxx/include/__config</description>
        <pubDate>Wed, 22 Jun 2022 08:11:14 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
</channel>
</rss>
