# GCC 17 poised to add native AArch64 Darwin support for Apple Silicon Macs

> **Key takeaway:** A patch series from longtime developer Iain Sandoe could finally upstream native AArch64 Darwin compilation into GCC after six years of out-of-tree maintenance by Homebrew and MacPorts.

**Published:** 2026-11-16T11:25:16+00:00 
**Source:** Phoronix Benchmarks &amp; Drivers 
**Category:** kernel-os 
**Canonical URL:** https://fosswire.org/news/gcc-17-poised-to-add-native-aarch64-darwin-support-for-apple.html 

## Summary
The GNU Compiler Collection may finally gain first-class native support for compiling to Apple's AArch64-based Darwin platform in the upcoming GCC 17 release. Developer Iain Sandoe submitted a patch series that has already been shipping in Homebrew and MacPorts builds of GCC since the GCC 10 era in 2020, but never merged into upstream GNU sources. The patches enable GCC to generate native binaries for macOS running on Apple Silicon without relying on external patches or cross-compilation workarounds.

GCC 17 feature development is nearing its freeze, though new ports traditionally receive some scheduling flexibility. If accepted, the change would reach stable form in GCC 17.1, expected around March or April 2027. This would mark the first time upstream GCC can directly target modern Apple Silicon Macs as a supported platform.

## What the AArch64 Darwin port changes
- **New platform target:** The patch series adds native AArch64 Darwin as a recognized GCC target triple, enabling direct compilation for macOS on Apple Silicon without downstream patching.
- **Proven codebase:** The same patches have been continuously maintained and shipped since 2020 in Homebrew and MacPorts GCC builds, giving the port extensive real-world testing across diverse workloads.
- **Release timing:** GCC 17 feature development is ending, but new ports typically receive extended review windows; Sandoe is explicitly targeting this release cycle rather than waiting for GCC 18.
- **Historical gap:** Apple Silicon Macs launched in 2020 with GCC 10 already in development, yet upstream GCC has lacked native support for the entire lifespan of the architecture to date.

## Why it matters
Upstream integration eliminates a significant maintenance burden for macOS package managers and developers who currently rely on patched GCC builds for scientific computing, cross-platform development, and open-source software compilation on Apple Silicon. For the broader open-source toolchain ecosystem, this reduces fragmentation between LLVM/Clang—which Apple actively maintains—and GCC, ensuring that performance-critical and GPL-licensed projects can build natively on modern Mac hardware without vendor-specific compiler lock-in.