* M1 support
@ 2021-06-12 22:00 Marek Borowski
2021-06-14 8:58 ` Jonathan Wakely
0 siblings, 1 reply; 3+ messages in thread
From: Marek Borowski @ 2021-06-12 22:00 UTC (permalink / raw)
To: gcc-help
Hi,
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? What are the blockers?
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.
If somebody could point me to better resources I would appreciate.
Regards
Marek Borowski
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: M1 support
2021-06-12 22:00 M1 support Marek Borowski
@ 2021-06-14 8:58 ` Jonathan Wakely
2021-06-14 14:46 ` Segher Boessenkool
0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Wakely @ 2021-06-14 8:58 UTC (permalink / raw)
To: Marek Borowski; +Cc: gcc-help
On Sat, 12 Jun 2021 at 23:01, Marek Borowski wrote:
>
> Hi,
>
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: M1 support
2021-06-14 8:58 ` Jonathan Wakely
@ 2021-06-14 14:46 ` Segher Boessenkool
0 siblings, 0 replies; 3+ messages in thread
From: Segher Boessenkool @ 2021-06-14 14:46 UTC (permalink / raw)
To: Jonathan Wakely; +Cc: Marek Borowski, gcc-help
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-06-14 14:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-12 22:00 M1 support Marek Borowski
2021-06-14 8:58 ` Jonathan Wakely
2021-06-14 14:46 ` Segher Boessenkool
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).