6 Commits

Author SHA1 Message Date
Nathan Corbyn
63ea3537d5
[libunwind](TestOnly) Mark failing tests as unsupported on Apple targets (#170488)
#167642 introduced a number of test failures on one of our stage 2
builds:
https://ci.swift.org/job/llvm.org/job/clang-stage2-Rthinlto/1403/. This
PR marks these tests as unsupported on `.*-apple.*` targets.
2025-12-03 18:17:54 +00:00
Gleb Popov
33bcde0678
libunwind: Remove OS requirements from tests to make them run on more OSes (#167642)
There might be a cleaner way to enable these tests running on FreeBSD,
I'm open to suggestions.

Co-authored-by: Alexander Richardson <mail@alexrichardson.me>
2025-12-01 12:05:37 -08:00
Louis Dionne
4f80c064eb
[runtimes][NFC] Consistently declare main() functions in tests (#162548)
In the libc++ test suite, we consistently declare main() functions with
full parameters and explicitly return from the function. This helps code
that compiles the tests with -ffreestanding, where main() is not a
special function (with an implicit return and special mangling).

This patch fixes a few stray declarations, including in libunwind and
libc++abi.
2025-10-09 09:00:20 -04:00
Wu Yingcong
4aaf6d1b8c
[libunwind][test] Add check for objcopy to improve test compatibility (#161112)
Previously, we only used `objcopy`, which is not available for some
build configurations. With this patch, we not only try to use `objcopy`,
but also try to use `llvm-objcopy` if available.

This is a follow-up of https://github.com/llvm/llvm-project/pull/156383.
2025-10-02 07:42:43 +08:00
Wu Yingcong
1af19772e6
[libunwind][test] set fed test to require x86 as others arch may have cross toolchain build (#156383)
In https://github.com/llvm/llvm-project/pull/154902, the test failed
with llvm-clang-win-x-aarch64(it is a cross-build, which builds on
Windows and run on Linux, "Win to Aarch64 Linux Ubuntu Cross
Toolchain"), and objdump is not available on Windows(the build env).
Set to require x86 Linux instead.
2025-09-02 19:30:44 +08:00
Wu Yingcong
e57f0e928d
[libunwind] fix pc range condition check bug (#154902)
There is an off-by-one error with current condition check for PC fallen
into the range or not. There is another check within libunwind that use
the correct checks in
5050da7ba1/libunwind/src/UnwindCursor.hpp (L2757)
```
      if ((fdeInfo.pcStart <= pc) && (pc < fdeInfo.pcEnd))
```
2025-09-01 09:15:52 +08:00