News for hackers. Stuff that matters.

A comment on Go in Go. Parent comment

Re:Go in Go by Aissen on Wednesday May 27, 2015 @04:08AM (#9609989)
Yes. It means that anytime you want to add a new supported architecture, you'll need to bootstrap through Go 1.4.

Otherwise, I'm guessing that for Go 1.6, they'll rely on you having a binary distribution of 1.5 (probably from your distribution, or their website), etc.

[ Parent | on HN ]
Re:Go in Go by EdiX on Wednesday May 27, 2015 @06:55AM (#9610478)
>It means that anytime you want to add a new supported architecture, you'll need to bootstrap through Go 1.4.

That's not true at all, (1) you write the backend for the target machine, (2) you recompile the compiler with the new backend included on a supported host, (3) then use the new compiler to compile itself for the target using the new backend, (4) you now have a compiler that runs on the target.

Same process is used to port C compilers (or any self-hosting compiler, really).

[ Parent | on HN ]
Re:Go in Go by jballanc on Wednesday May 27, 2015 @04:51AM (#9610115)
I think it would be much more likely that new architectures would be added as cross-compilation targets than to work back through a v1.4 bootstrap.
[ Parent | on HN ]