Louis Dionne 8f90e6937a [runtimes] Use LLVM libunwind from libc++abi by default (#77687) ... I recently came across LIBCXXABI_USE_LLVM_UNWINDER and was surprised to notice it was disabled by default. Since we build libunwind by default and ship it in the LLVM toolchain, it would seem to make sense that libc++ and libc++abi rely on libunwind for unwinding instead of using the system-provided unwinding library (if any). Most importantly, using the system unwinder implies that libc++abi is ABI compatible with that system unwinder, which is not necessarily the case. Hence, it makes a lot more sense to instead default to using the known-to-be-compatible LLVM unwinder, and let vendors manually select a different unwinder if desired. As a follow-up change, we should probably apply the same default to compiler-rt. Differential Revision: https://reviews.llvm.org/D150897 Fixes #77662 rdar://120801778		2024-01-11 10:13:21 -05:00
..
workflows	[runtimes] Use LLVM libunwind from libc++abi by default (#77687)	2024-01-11 10:13:21 -05:00
CODEOWNERS	Update CODEOWNERS	2024-01-01 18:12:49 -08:00
new-issues-labeler.yml	Fix issue labeler applying incorrect label for libc++abi issues (#67811)	2023-09-29 18:46:42 +04:00
new-prs-labeler.yml	new-prs-labeler: update clang:dataflow paths (#72153)	2023-11-14 11:07:37 +01:00