[llvm-branch-commits] [libcxx] [libc++] Adds a FTM v2 data file generator. (PR #134555)

2025-04-06 Thread Mark de Wever via llvm-branch-commits
@@ -2579,11 +2639,32 @@ def generate_header_test_directory(self, path: os.path) -> None: def main(): +# +# Note this generator switches from the data structures in this file (v1) +# to data structures in an external json file (v2). This project is in its +# t

[llvm-branch-commits] [llvm] [libc++][CI] Pin the XCode version. (PR #135412)

2025-04-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/135412 This version is the current version, to avoid unplanned automatic updates in the future pin this version. >From 3ba88a658be638776bbf54da3f1a0d41fe8756c1 Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Fri,

[llvm-branch-commits] [llvm] [libc++][CI] Pin the XCode version. (PR #135412)

2025-04-11 Thread Mark de Wever via llvm-branch-commits
mordante wrote: I agree Louis should chime in when he's back. I just want to make sure we have a patch to pin this so things remain stable until that time. It seems this broke when switching from the 16.3 beta/rc? 1.to the final version. I've added the bug report to my list of things to discus

[llvm-branch-commits] [libcxx] release/20.x: [libc++] Fix misplaced _LIBCPP_POP_MACROS (#134874) (PR #134895)

2025-04-11 Thread Mark de Wever via llvm-branch-commits
mordante wrote: > Are these test failures relevant? No there was an issue with the AIX-32 build bot last week. https://github.com/llvm/llvm-project/pull/134895 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.

[llvm-branch-commits] [libcxx] [libc++] Adds a FTM v2 data file generator. (PR #134555)

2025-04-12 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante edited https://github.com/llvm/llvm-project/pull/134555 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [libcxx] [libc++][CI] Update action runner base image. (PR #130433)

2025-03-08 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/130433 Updates to the latest release. The side effect of this change is updating all compilers to the latest upstream version. >From 02c75830fe16e7de91d8406d9422575bc560fac2 Mon Sep 17 00:00:00 2001 From: Mark de Wev

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-09 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/130500 The followup paper P3235R3 which is voted in as a DR changes the names foo_locking to foo_buffered. These changes have been applied in this patch. Before ---

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From 3858aba918b9c3d472567367688c67bc6fa08d6b Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH] [libc++][format] Implements P3107R5 in . The followup paper P3

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From 4bd6795cb216306d4b4a1993057f651a3d6e734b Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH] [libc++][format] Implements P3107R5 in . The followup paper P3

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From 053213aa92526e6fccb5824ac2e3e704cebb9a7a Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH] [libc++][format] Implements P3107R5 in . The followup paper P3

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From 3efe358f31aa13267142dd40a0eb7f401ba65794 Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH] [libc++][format] Implements P3107R5 in . The followup paper P3

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-13 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From c132aa555a38efde9b04c2a3f435ba598778c28d Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH 1/2] [libc++][format] Implements P3107R5 in . The followup pape

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-13 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From c132aa555a38efde9b04c2a3f435ba598778c28d Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH 1/2] [libc++][format] Implements P3107R5 in . The followup pape

[llvm-branch-commits] [libcxx] [libc++] Clang-tidy operator& hijacker. (PR #128366)

2025-03-12 Thread Mark de Wever via llvm-branch-commits
mordante wrote: > This check should be in regular Clang Tidy, using of `std::addressof` actual > not only for libbcpp, any user-writted code might follow the guidline to use > `std::addressof` instead of `operator&` for a generic type. For example, the > Boost library: > https://github.com/bo

[llvm-branch-commits] [libcxx] [libc++][format] Implements P3107R5 in . (PR #130500)

2025-03-11 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/130500 >From 17b0a346132bcc65de1aefc4d4654bd00e1e473d Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sat, 30 Mar 2024 17:35:56 +0100 Subject: [PATCH] [libc++][format] Implements P3107R5 in . The followup paper P3

[llvm-branch-commits] [libcxx] [NFC][libc++] Guard agains operator& hijacking. (PR #128351)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/128351 This set usage of operator& instead of std::addressof seems not be easy to "abuse". Some seem easy to misuse, like basic_ostream::operator<<, trying to do that results in compilation errors since the `widen` f

[llvm-branch-commits] [libcxx] [NFC][libc++] Guard agains operator& hijacking. (PR #128351)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/128351 >From 921a76f2275b2bde219a9f0a7a434da1f22294f9 Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sun, 16 Feb 2025 13:25:15 +0100 Subject: [PATCH] [NFC][libc++] Guard agains operator& hijacking. This set usage

[llvm-branch-commits] [libcxx] [NFC][libc++] Guard agains operator& hijacking. (PR #128351)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/128351 >From 05c33c80b15e9f1cd27206f31ff69add583f72af Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sun, 16 Feb 2025 13:25:15 +0100 Subject: [PATCH] [NFC][libc++] Guard agains operator& hijacking. This set usage

[llvm-branch-commits] [libcxx] [libc++] Clang-tidy operator& hijacker. (PR #128366)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante updated https://github.com/llvm/llvm-project/pull/128366 >From ab09f9dfbc3ee01af586b8a5285ac72b4f35e2f9 Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sun, 16 Feb 2025 12:07:44 +0100 Subject: [PATCH] [libc++] Clang-tidy operator& hijacker. Guards against introdu

[llvm-branch-commits] [libcxx] [libc++] Clang-tidy operator& hijacker. (PR #128366)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/128366 Guards against introducing new places where operator& depends on a template type. >From 5a96aadb54b757812dc48f07e753477164d8062a Mon Sep 17 00:00:00 2001 From: Mark de Wever Date: Sun, 16 Feb 2025 12:07:44 +0

[llvm-branch-commits] [libcxx] [NFC][libc++] Guard against operator& hijacking. (PR #128351)

2025-02-22 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante edited https://github.com/llvm/llvm-project/pull/128351 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [libcxx] [libc++] Implements the new FTM documentation generator. (PR #139774)

2025-05-13 Thread Mark de Wever via llvm-branch-commits
https://github.com/mordante created https://github.com/llvm/llvm-project/pull/139774 The new documentation will look like https://discourse.llvm.org/t/rfc-improving-the-feature-test-macro-status-page/78327/5?u=mordante Rate limit ยท GitHub body { b

<    1   2   3