<?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 run-buildbot</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2fb8f67e - [libc++] Allow enabling assertions when back-deploying</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#2fb8f67e</link>
        <description>[libc++] Allow enabling assertions when back-deployingWhen back-deploying to older platforms, we can still provide assertions,but we might not be able to provide a great implementation for the verbosehandler. Instead, we can just call ::abort().Differential Revision: https://reviews.llvm.org/D131199(cherry picked from commit e36f9e13bca41223bd6af7e49bf020e58a676e9d)

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 04 Aug 2022 19:25:48 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f1c30135 - [libc++] Drop the legacy debug mode symbols by default</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#f1c30135</link>
        <description>[libc++] Drop the legacy debug mode symbols by defaultLeave the escape hatch in place with a note, but don&apos;t include thedebug mode symbols by default since we don&apos;t support the debug modein the normal library anymore.This is technically an ABI break for users who were depending onthose debug mode symbols in the dylib, however those users willalready be broken at compile-time because they must have been using_LIBCPP_DEBUG=2, which is now an error.Differential Revision: https://reviews.llvm.org/D127360

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 19 Jul 2022 15:04:31 +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/utils/ci/run-buildbot#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/utils/ci/run-buildbot</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>7300a651 - [libc++] Re-apply &quot;Always build c++experimental.a&quot;&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#7300a651</link>
        <description>[libc++] Re-apply &quot;Always build c++experimental.a&quot;&quot;This re-applies bb939931a1ad, which had been reverted by 09cebfb978debecause it broke Chromium. The issues seen by Chromium should beaddressed by 1d0f79558ca4.Differential Revision: https://reviews.llvm.org/D128927

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 19 Jul 2022 14:44:06 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>09cebfb9 - Revert &quot;[libc++] Always build c++experimental.a&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#09cebfb9</link>
        <description>Revert &quot;[libc++] Always build c++experimental.a&quot;This caused build failures when building Clang and libc++ together on Mac:  fatal error: &apos;experimental/memory_resource&apos; file not foundSee the code review for details. Reverting until the problem and how tosolve it is better understood.(Updates to some test files were not reverted, since they seemedunrelated and were later updated by 340b48b267b96.)&gt; This is the first part of a plan to ship experimental features&gt; by default while guarding them behind a compiler flag to avoid&gt; users accidentally depending on them. Subsequent patches will&gt; also encompass incomplete features (such as &lt;format&gt; and &lt;ranges&gt;)&gt; in that categorization. Basically, the idea is that we always&gt; build and ship the c++experimental library, however users can&apos;t&gt; use what&apos;s in it unless they pass the `-funstable` flag to Clang.&gt;&gt; Note that this patch intentionally does not start guarding&gt; existing &lt;experimental/FOO&gt; content behind the flag, because&gt; that would merely break users that might be relying on such&gt; content being in the headers unconditionally. Instead, we&gt; should start guarding new TSes behind the flag, and get rid&gt; of the existing TSes we have by shipping their Standard&gt; counterpart.&gt;&gt; Also, this patch must jump through a few hoops like defining&gt; _LIBCPP_ENABLE_EXPERIMENTAL because we still support compilers&gt; that do not implement -funstable yet.&gt;&gt; Differential Revision: https://reviews.llvm.org/D128927This reverts commit bb939931a1adb9a47a2de13c359d6a72aeb277c8.

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Mon, 18 Jul 2022 14:34:34 +0000</pubDate>
        <dc:creator>Hans Wennborg &lt;hans@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>bb939931 - [libc++] Always build c++experimental.a</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#bb939931</link>
        <description>[libc++] Always build c++experimental.aThis is the first part of a plan to ship experimental featuresby default while guarding them behind a compiler flag to avoidusers accidentally depending on them. Subsequent patches willalso encompass incomplete features (such as &lt;format&gt; and &lt;ranges&gt;)in that categorization. Basically, the idea is that we alwaysbuild and ship the c++experimental library, however users can&apos;tuse what&apos;s in it unless they pass the `-funstable` flag to Clang.Note that this patch intentionally does not start guardingexisting &lt;experimental/FOO&gt; content behind the flag, becausethat would merely break users that might be relying on suchcontent being in the headers unconditionally. Instead, weshould start guarding new TSes behind the flag, and get ridof the existing TSes we have by shipping their Standardcounterpart.Also, this patch must jump through a few hoops like defining_LIBCPP_ENABLE_EXPERIMENTAL because we still support compilersthat do not implement -funstable yet.Differential Revision: https://reviews.llvm.org/D128927

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 30 Jun 2022 15:24:43 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>de4a57cb - [libc++] Re-add transitive includes that had been removed since LLVM 14</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#de4a57cb</link>
        <description>[libc++] Re-add transitive includes that had been removed since LLVM 14This commit re-adds transitive includes that had been removed by4cd04d1687f1, c36870c8e79c, a83f4b9cda57, 1458458b558d, 2e2f3158c604,and 489637e66dd3. This should cover almost all the includes that hadbeen removed since LLVM 14 and that would contribute to breaking usercode when releasing LLVM 15.It is possible to disable the inclusion of these headers by defining_LIBCPP_REMOVE_TRANSITIVE_INCLUDES. The intent is that vendors willenable that macro and start fixing downstream issues immediately. Wecan then remove the macro (and the transitive includes) by default ina future release. That way, we will break users only once by removingtransitive includes in bulk instead of doing it bit by bit a everyrelease, which is more disruptive for users.Note 1: The set of headers to re-add was found by re-generating the        transitive include test on a checkout of release/14.x, which        provided the list of all transitive includes we used to provide.Note 2: Several includes of &lt;vector&gt;, &lt;optional&gt;, &lt;array&gt; and &lt;unordered_map&gt;        have been added in this commit. These transitive inclusions were        added when we implemented boyer_moore_searcher in &lt;functional&gt;.Note 3: This is a best effort patch to try and resolve downstream breakage        caused since branching LLVM 14. I wasn&apos;t able to perfectly mirror        transitive includes in LLVM 14 for a few headers, so I added a        release note explaining it. To summarize, adding boyer_moore_searcher        created a bunch of circular dependencies, so we have to break        backwards compatibility in a few cases.Differential Revision: https://reviews.llvm.org/D128661

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Mon, 27 Jun 2022 19:53:41 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>eb12ad9d - [libc++][CI] Updates GCC to version 12.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#eb12ad9d</link>
        <description>[libc++][CI] Updates GCC to version 12.Reviewed By: ldionne, philnik, #libc, #libc_abiDifferential Revision: https://reviews.llvm.org/D126667

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Mon, 30 May 2022 16:38:27 +0000</pubDate>
        <dc:creator>Mark de Wever &lt;koraq@xs4all.nl&gt;</dc:creator>
    </item>
<item>
        <title>3af7aa52 - [libcxx][AIX] Enable ABI list checking for XCOFF</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#3af7aa52</link>
        <description>[libcxx][AIX] Enable ABI list checking for XCOFFThe existing nm extractors can&apos;t dump the loader symbol table information we need to do the ABI checks for XCOFF, so provide an implementation using the system dump utility. We match the symbol name, whether it&apos;s defined, it&apos;s import/export status, and its storage mapping class.Reviewed By: #libc, ldionneDifferential Revision: https://reviews.llvm.org/D124165

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 14 Jun 2022 17:15:46 +0000</pubDate>
        <dc:creator>Jake Egan &lt;jakeegan10@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>1cf41139 - [libcxx][AIX] Switch build compiler to clang</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#1cf41139</link>
        <description>[libcxx][AIX] Switch build compiler to clangThis patch switches the build compiler for AIX from ibm-clang to clang. ibm-clang++_r has `-pthread` by default, but clang for AIX doesn&apos;t, so `-pthread` had to be added to the test config. A bunch of tests now pass, so the `XFAIL` was removed. This patch also switch the build to use the visibility support available in clang-15 to control symbols exported by the shared library (AIX traditionally uses explicit export lists for this purpose).Reviewed By: #libc, #libc_abi, daltenty, #libunwind, ldionneDifferential Revision: https://reviews.llvm.org/D127470

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 14 Jun 2022 01:44:58 +0000</pubDate>
        <dc:creator>Jake Egan &lt;jakeegan10@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/utils/ci/run-buildbot#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/utils/ci/run-buildbot</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>222bd83d - [libc++] Forgot to bump the CI timeout everywhere</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#222bd83d</link>
        <description>[libc++] Forgot to bump the CI timeout everywhere

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 07 Jun 2022 14:01:01 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>76c7e1f2 - [libc++] Bump timeout to avoid spurious failures on AIX</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#76c7e1f2</link>
        <description>[libc++] Bump timeout to avoid spurious failures on AIX

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 07 Jun 2022 14:00:25 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>dfaee3c9 - [libunwind][ci][AIX] Add libunwind to buildbot CI</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#dfaee3c9</link>
        <description>[libunwind][ci][AIX] Add libunwind to buildbot CISummary:This patch changes scripts to add libunwind CI on AIX. Test config file ibm-libunwind-shared.cfg.in is introduced for testing on AIX.Reviewed by: ldionne, MaskRay, libunwind, ibc++abiDifferential Revision: https://reviews.llvm.org/D126017

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 02 Jun 2022 13:03:10 +0000</pubDate>
        <dc:creator>Xing Xue &lt;xingxue@outlook.com&gt;</dc:creator>
    </item>
<item>
        <title>719bf2d9 - [runtimes] Officially deprecate the legacy testing configuration system</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#719bf2d9</link>
        <description>[runtimes] Officially deprecate the legacy testing configuration systemAdd a warning and tweak the release note to explain that the deprecationtargets libc++, libc++abi and libuwnind as well.Also, as a fly-by, ensure that our CI runs the legacy testing configurationfor libc++, libc++abi and libunwind. This doesn&apos;t matter too much sinceit&apos;s deprecated, but we might as well test it properly.Differential Revision: https://reviews.llvm.org/D126478

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 26 May 2022 15:12:45 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>92bbcfaa - [libunwind] Tidy-up the testing configuration for libunwind</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#92bbcfaa</link>
        <description>[libunwind] Tidy-up the testing configuration for libunwindStart testing Apple backdeployment with older libunwinds, and stopexplicitly specifying the libunwind testing config, since it isalready selected correctly by default.Differential Revision: https://reviews.llvm.org/D126470

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 26 May 2022 14:19:25 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>3bba72e6 - [libc++] Time tests during CI</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#3bba72e6</link>
        <description>[libc++] Time tests during CI

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Thu, 26 May 2022 18:58:24 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a9a6e200 - [libc++] Rename the generic-singlethreaded CI job to generic-no-threads for consistency</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#a9a6e200</link>
        <description>[libc++] Rename the generic-singlethreaded CI job to generic-no-threads for consistency

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Tue, 24 May 2022 13:58:04 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>fa7ce8e6 - [runtimes] Fix the build of merged ABI/unwinder libraries</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#fa7ce8e6</link>
        <description>[runtimes] Fix the build of merged ABI/unwinder librariesAlso, add a CI job that tests this configuration. The exact configurationis that we build a shared libc++ and merge objects for the ABI libraryand the unwinder library into it.Differential Revision: https://reviews.llvm.org/D125903

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Wed, 18 May 2022 16:05:45 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>30194d45 - [libcxx] [ci] Add a i386 Windows configuration to CI</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/utils/ci/run-buildbot#30194d45</link>
        <description>[libcxx] [ci] Add a i386 Windows configuration to CIAdding a mingw based config is easy in the current CI environment(where we can just choose the different target by calling`i686-w64-mingw32-clang`), while adding a clang-cl based config wouldrequire setting up different environment variables pointing to thei386 library directory.Just adding one config (DLL) instead of exhaustively testing both(DLL and static) as very few tests would differ in practice, to keepthe CI load reasonable.Differential Revision: https://reviews.llvm.org/D124991

            List of files:
            /llvm-project-15.0.7/libcxx/utils/ci/run-buildbot</description>
        <pubDate>Wed, 04 May 2022 08:05:44 +0000</pubDate>
        <dc:creator>Martin Storsj&#246; &lt;martin@martin.st&gt;</dc:creator>
    </item>
</channel>
</rss>
