2 ms·

Ah ok, so there will be a pretty long chain from 1.2 eventually, but hopefully it will be part of the test suite...

• jlouis 12y ago
  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.
• enneff 12y ago
  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.
  • TheLoneWolfling 12y ago
    Where is this fact documented? Are patches tested against 1.4 tool chain binaries?
    • madhusudancs 12y ago
      Here https://docs.google.com/document/d/1OaatvGhEAq7VseQ9kkavxKNAfepWy2yhPUBs96FGV28/edit https://docs.google.com/document/d/1OaatvGhEAq7VseQ9kkavxKNA... In the proposal section.
    • enneff 12y ago
      > Where is this fact documented? http://tip.golang.org/doc/install/source#go14 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.)