Golang on ARM
github.com
Golang on ARM
1–10 of 71 posts
Re: Golang on ARM
#2Isn't the best course usually to build a solid foundation, then branch out?
Re: Golang on ARM
#3I'm not aware of anything that even comes close to tooling out cross compilation so easily.
Re: Golang on ARM
#4Maybe I'm in the minority but I would rather have resources devoted to improving compile times in 1.5+ versions vs. having golang work on arm. Isn't the best course usually to build a solid foundation, then branch out?
That said, the counterpoint is that cross-compilation is not something you can easily bolt on later -- if you aren't doing, and testing it along the way, you will never be able to add it back in. It needs to be there from the beginning and stay a first-class support goal, otherwise mistakes, good intentions and laziness will all yield a product that just can't easily make the leap back to solid cross compilation with no hassle.
Re: Golang on ARM
#5I realize that standard towers may be supplanted by their SoC brethren, but so what? Will we all be using iMac-like computers as desktops in the next 36-72 months? Will there even be any differentiation between "regular" desktops with discrete CPUs, memory, etc and the system-on-a-chip variant?
Re: Golang on ARM
#6Maybe I'm in the minority but I would rather have resources devoted to improving compile times in 1.5+ versions vs. having golang work on arm. Isn't the best course usually to build a solid foundation, then branch out?
I'd also like to see Go on MIPS64, though probably less important than ARM.
Re: Golang on ARM
#7This is for both development on ARM systems (standard go commands, eg: go build, etc) and deploying to ARM systems (setting ARM as a compile target). That said, I'm genuinely curious why anyone would develop on an ARM-based system as opposed to your run of the mill desktop. I realize that standard towers may be supplanted by their SoC brethren, but so what? Will we all be using iMac-like computers as desktops in the…
Re: Golang on ARM
#8Maybe I'm in the minority but I would rather have resources devoted to improving compile times in 1.5+ versions vs. having golang work on arm. Isn't the best course usually to build a solid foundation, then branch out?
Re: Golang on ARM
#9Re: Golang on ARM
#10How about the support by the LLVM. Shouldn't this be enough?