[all-commits] [llvm/llvm-project] 8c8f32: [compiler-rt] Don't run arm64e builtins tests on d...

[Ahmed Bougacha via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 8c8f3286a72c0d3bc07871b31eb7409801a8a380
      https://github.com/llvm/llvm-project/commit/8c8f3286a72c0d3bc07871b31eb7409801a8a380
  Author: Ahmed Bougacha <ahmed at bougacha.org>
  Date:   2025-08-13 (Wed, 13 Aug 2025)

  Changed paths:
    M compiler-rt/cmake/Modules/CompilerRTDarwinUtils.cmake

  Log Message:
  -----------
  [compiler-rt] Don't run arm64e builtins tests on darwin. (#153312)

The compiler-rt build gradually learned to target arm64e. With that, we
build builtins for arm64e, but running their tests usually isn't
possible, because most versions of macOS so far restrict arm64e (on
account of its unstable ABI).

Starting with macOS 26, arm64e executables can be run, because the
aligned linker automatically targets ptrauth ABI version 1. Without
that, (at ABI version 0) these can't be executed.

We can't rely or require new linkers (and we elsewhere explicitly
fallback to ld classic anyway), so in the meantime one way to execute
these would be to explicitly ask for ABI version 1, which we generally
try to avoid, and don't support in our llvm (which unconditionally
targets ABI version 0).

This is also an uncommon situation; sanitizer runtime tests aren't run
on arm64e today, because we haven't listed arm64e as a supported arch
yet.
Everything other than builtins also tests for execution in cmake first;
we should consider that, but it has its own problems.

So we can simply disable arm64e from tests, by filtering it out as a
valid darwin host arch, which accurately reflects reality.

When we try to add arm64e sanitizer runtime build and test support,
we'll want to change that, but that's a bigger problem than builtins.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications