represent Mac Catalyst as aarch64-maccatalyst-none rather than aarch64-ios-macabi

Apple's own headers and tbd files prefer to think of Mac Catalyst as a distinct
OS target. Earlier, when DriverKit support was added to LLVM, it was represented
a distinct OS. So why Apple decided to only represent Mac Catalyst as an ABI in
the target triple is beyond me. But this isn't the first time they've ignored
established target triple norms (see: armv7k and aarch64_32) and it probably
won't be the last.

While doing this, I also audited all Darwin OS prongs throughout the codebase
and made sure they cover all the tags.
This commit is contained in:
Alex Rønne Petersen
2025-11-13 18:05:46 +01:00
parent 2e6f7d36b9
commit 9ab7eec23e
46 changed files with 273 additions and 241 deletions
+1 -1
View File
@@ -1398,7 +1398,7 @@ test "allocation and looping over 3-byte integer" {
if (builtin.zig_backend == .stage2_spirv) return error.SkipZigTest;
if (builtin.zig_backend == .stage2_riscv64) return error.SkipZigTest;
if (builtin.zig_backend == .stage2_llvm and builtin.os.tag == .macos) {
if (builtin.zig_backend == .stage2_llvm and builtin.os.tag.isDarwin()) {
return error.SkipZigTest; // TODO
}
if (builtin.cpu.arch == .s390x and builtin.zig_backend == .stage2_llvm) return error.SkipZigTest; // TODO