Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

I'm not making any function calls in the assembly, just writing to memory addresses that represent the elements / len of the slice. I've also tried using LockOSThread() to see if that made any difference, alas it does not. On Friday, March 22, 2019 at 4:59:30 AM UTC-7, Robert Engels wrote: > >

Re: [go-nuts] Accessing *[]uint64 from assembly - strange memory corruption under heavy load - any ideas?

The assembly should never write to a position / update the len beyond the backing array (specifically, the assembly is generated from code where the 'max stack depth' has been computed and validated, and the capacity of the slice is that size). On Friday, March 22, 2019 at 5:39:36 AM UTC-7,

Re: [go-nuts] Golang asm to real asm table/doc/tool

Sorry, where is oplook, buildop and asmout? On Wednesday, November 30, 2016 at 7:43:25 AM UTC+11, Aram Hăvărneanu wrote: > > On Tue, Nov 29, 2016 at 8:59 PM, matt > wrote: > > Where in the source code does it map say MOVBU.P to ldrb post increment? > > It's