Just wondering if anyone had info on the effort required to make the Go programming language work on a Propeller chip. I'm sure the first challenge would be the considerable memory required - a rather complete runtime is embedded in the output executable for even somewhat trivial applications compiled from Go - a "hello world" program compiled on my Mac laptop outputs a 2.2mb executable, and it's common for more complex programs that use other parts of the std lib to be more like 8-12mb on disk. But assuming one were using XMM (or other appropriate memory model - I don't claim to have a comprehensive understanding of propeller architecture, I'm only casually acquainted with writing Spin and C on a propeller) and potentially an add-on chip with additional memory (flash or otherwise), and some restrictions on which parts of the std lib are supported - it seems like it would be possible.
In contrast with languages like Python and Java, Go outputs native executables. There's no byte code, and the runtime is included into the output, which I think helps matters in terms of overall simplicity (although it makes for a bigger output).
All that said, I was just curious if anyone has any sort of assessment of what effort would be required to do a port like this? I very much like the propeller multicore architecture, and while I see the point of Spin, and am aware of Propeller ASM, and I've used the C compiler, it just isn't the same as being able to work in a higher level language. Maybe it's just too heavy for this environment, but I'm interested to see what other people think about this.