News for hackers. Stuff that matters.
Re:“This change deletes the C implementations of the Go comp... by justincormack on Monday February 23, 2015 @06:11PM (#9097668)
Ah ok, so there will be a pretty long chain from 1.2 eventually, but hopefully it will be part of the test suite...
Re:“This change deletes the C implementations of the Go comp... by enneff on Monday February 23, 2015 @06:17PM (#9097694)
You should always be able to build a Go 1.x compiler with just the 1.4 tool chain binaries. We have committed to sticking to the Go 1.4 language and libraries for the compiler tool chain.
Re:“This change deletes the C implementations of the Go comp... by TheLoneWolfling on Monday February 23, 2015 @08:50PM (#9098288)
Where is this fact documented? Are patches tested against 1.4 tool chain binaries?
Re:“This change deletes the C implementations of the Go comp... by enneff on Tuesday February 24, 2015 @12:04AM (#9098822)
> Where is this fact documented?

http://tip.golang.org/doc/install/source#go14

> Are patches tested against 1.4 tool chain binaries?

The builders build the tool chain with Go 1.4, so the build dashboard will show failures if a patch incompatible with 1.4 is submitted. (We have pre-commit trybots that do the same.)

Re:“This change deletes the C implementations of the Go comp... by madhusudancs on Monday February 23, 2015 @11:05PM (#9098616)
Re:“This change deletes the C implementations of the Go comp... by jlouis on Monday February 23, 2015 @06:15PM (#9097681)
Usually you don't keep the chain. You just keep a working compiler. You can also bootstrap from another implementation of the language, e.g., gccgo.

A common trick is to keep a highly portable interpreted version of the target language and then use this for bootstrapping, but often you attack new architectures by cross-compilation instead. It all depends.

Also, it is common for self-hosting languages to require themselves to build.