arrowd wrote:
I'm missing why the test is getting run at all on macos, despite me putting
`UNSUPPORTED: system-darwin`?
https://github.com/llvm/llvm-project/pull/167642
___
cfe-commits mailing list
cfe-commits@lists.
arrowd wrote:
I have removed all OS requirements from tests to see the CI fallout. I'll add
`UNSUPPORTED` clauses based on the build results.
https://github.com/llvm/llvm-project/pull/167642
___
cfe-commits mailing list
[email protected]
http
https://github.com/arrowd updated
https://github.com/llvm/llvm-project/pull/167642
>From 936acb229e7d6436409882aefea903044531367d Mon Sep 17 00:00:00 2001
From: Gleb Popov <[email protected]>
Date: Tue, 30 Sep 2025 13:59:25 +0300
Subject: [PATCH] libunwind: Remove OS requirements from tests to
https://github.com/arrowd edited
https://github.com/llvm/llvm-project/pull/167642
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/arrowd updated
https://github.com/llvm/llvm-project/pull/167642
>From 087dad9d9eb5a7e0280e7a1217cc1ce6b2a7a196 Mon Sep 17 00:00:00 2001
From: Gleb Popov <[email protected]>
Date: Tue, 30 Sep 2025 13:59:25 +0300
Subject: [PATCH] libunwind: Remove OS requirements from tests to
https://github.com/arrowd updated
https://github.com/llvm/llvm-project/pull/160887
>From 4c133e4c7e1de87d8ac0d83ec2b8ea9e7089eab5 Mon Sep 17 00:00:00 2001
From: Gleb Popov <[email protected]>
Date: Fri, 26 Sep 2025 12:58:47 +0300
Subject: [PATCH] libunwind: Implement the unw_strerror function f
arrowd wrote:
What's required to move this forward?
https://github.com/llvm/llvm-project/pull/160887
___
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/arrowd created
https://github.com/llvm/llvm-project/pull/160887
As it was explained to me in
https://discourse.llvm.org/t/libunwinds-raison-detre/88283/2 the LLVM version
of libunwind is mostly compatible with nongnu one. This change improves the
compatibility a bit further
arrowd wrote:
> you could probably piggyback on bad_unwind_info.pass.cpp's second assert.
Turns out it isn't possible. `unw_step` returns a positive value in case of
success or 0 if there is nowhere to step. The nongnu libunwind's manpage says
that it also may return some error codes, but it i
arrowd wrote:
I just remembered that these strings are already present in the LLVM codebase:
https://github.com/llvm/llvm-project/blob/a4015d98d2ad3faba12d8c1a82942330852b9efd/libunwind/include/libunwind.h#L54-L67
https://github.com/llvm/llvm-project/pull/160887
https://github.com/arrowd updated
https://github.com/llvm/llvm-project/pull/160887
>From 76529236548e613a0f487b38c98f10b535538e18 Mon Sep 17 00:00:00 2001
From: Gleb Popov <[email protected]>
Date: Fri, 26 Sep 2025 12:58:47 +0300
Subject: [PATCH] libunwind: Implement the unw_strerror function f
11 matches
Mail list logo