Re: [go-nuts] Cross-compilation of golang assembly via 'go tool asm'

Thanks, great reference to gooOsArchFile() On Tuesday, September 13, 2016 at 11:04:44 AM UTC-6, ironi...@gmail.com wrote: > > > > On Tuesday, September 13, 2016 at 11:08:18 AM UTC-5, pcj...@gmail.com > wrote: >> >> My next question is which tool is responsible for selecting the correct >> sha1b

Re: [go-nuts] Cross-compilation of golang assembly via 'go tool asm'

Thanks Aram and Michael, that helps a lot. I've studied https://github.com/golang/go/tree/master/src/crypto/sha1 which looks like a good example of having a pure-go fallback with architecture-specific assembly. My next question is which tool is responsible for selecting the correct sha1blo

Re: [go-nuts] Cross-compilation of golang assembly via 'go tool asm'

On Monday, September 12, 2016 at 9:58:58 PM UTC-6, Michael Hudson-Doyle wrote: > > > > On 13 September 2016 at 13:43, > wrote: > >> I'm implementing cross-compilation support in rules_go >> . This takes a low-level >> approach to building golang targets

[go-nuts] Cross-compilation of golang assembly via 'go tool asm'

I'm implementing cross-compilation support in rules_go . This takes a low-level approach to building golang targets that involves use of the individual toolchain components such as 'go tool asm', 'go tool compile', 'go tool link', etc... Cross-compilatio