> The build flag -gcflags=-m will cause the compiler to report which 
> allocations escape to the heap.
> Give that a try and see what it tells you.

It doesn't report any escape info for that function. I did figure it
out by outcommenting parts of the function, it turns out that

scratch := f32scratch.Get(r2)
trow := scratch.buf[:r2]

are allocated on the heap, for some reason. Both are []float32 slices.
Oh, now i write this email i understand why the scratch buffer
escapes: at the end of the function it is put back on the sync.Pool
via a function call...
Thanks anyway!

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to