>>19
GCC as such is fine, as long as you don't have to deal with the back-end too much.
The problem is rather that the GCC port is inofficial, and Golang keeps using their own, shitty C Compiler.
And as far as I can tell, the only reason the goland folks are using their own compiler is because "it's faster", not because it's more... you know, portable.
As said before, Go is, in this current state, a serious bitch to port to anything else than Linux.