“This change deletes the C implementations of the Go compiler and assembler”

Maybe it matters less, you used to always assume bootstrap from C but that more or less died with C++ based compilers, although you can do a multistage bootstrap from the last gcc before C++ still.

Re: “This change deletes the C implementations of the Go compiler and assembler”

#7

Post by smegel » Mon, Feb 23, 2015, 11:00 PM UTC

And the boy pulled up his bootstraps and became a man.

Re: “This change deletes the C implementations of the Go compiler and assembler”

#8

Post by jvreeland » Mon, Feb 23, 2015, 11:00 PM UTC

[deleted] wrote: post #4

[deleted]

you'll still be able to see it if you check out an earlier version.

Re: “This change deletes the C implementations of the Go compiler and assembler”

#9

Post by gresrun » Mon, Feb 23, 2015, 11:01 PM UTC

Once you go Go, you never Go back!

Re: “This change deletes the C implementations of the Go compiler and assembler”

#10

Post by ori_b » Mon, Feb 23, 2015, 11:02 PM UTC

justincormack wrote: post #6

So what is the bootstrap process going to be? Other than already have a Go compiler I mean. Or is it have a Go cross compiler? Maybe it matters less, you used to always assume bootstrap from C but that more or less died with C++ based compilers, although you can do a multistage bootstrap from the last gcc before C++ still.

Either cross compile, or get the last C-based Go compiler, and use that to build the more recent Go releases.