On Mon, Jun 14, 2021 at 09:58:59AM +0100, Jonathan Wakely via Gcc-help wrote: > On Sat, 12 Jun 2021 at 23:01, Marek Borowski wrote: > > What I’m aware we still don’t have apple m1 support in gcc. Do you know what the current status is? Why is porting so slow? > > Because porting GCC is hard and takes a lot of work and testing. > > > What are the blockers? > > Time and resources. > > > I found https://github.com/iains/gcc-darwin-arm64 <https://github.com/iains/gcc-darwin-arm64> There some problem highlighted there. However it does not seem to be official repo. > > Iain is the darwin maintainer, so it's as official as anything until > the port gets committed upstream to gcc.gnu.org > > But he has a full-time job, and adding M1 support is just being done > in his spare time. And note none of this is about M1. aarch64-linux runs just fine on M1, for example. The problem is getting the Apple libraries etc. to work with the rest, so the OS side of things. M1 is just another aarch64 processor. Segher
