Of course you'll need a specific runtime just like for C you can't use the user space libc. There's no difference between C and Go here. You can create your ow

Of course you'll need a specific runtime just like for C you can't use the user space libc. There's no difference between C and Go here. You can create your own runtime as you see fit. In fact, the Go distribution used to ship with such a bare metal runtime. Search the repository history for the tiny runtime. Reviving it again should be easier then porting Go to a new architecture, which is quite easy. Making a stub runtime (equivalent to booting a C kernel with no libc) is not more than half an hour of work. Go can call assembly and C, and assembly and C can call Go. This is used a lot in the runtime, nothing special about it.