mercredi 20 octobre 2021

Go - Failing escape analysis on different slice headers with shared data

I'm working on a project where I frequently convert []int32 to []byte. I created a function intsToBytes to perform an inplace conversion to minimize copying. I noticed that Go's escape analysis doesn't realize that ints and bytes reference the same underlying data. As a result, ints is overwritten by the next function's stack data and bytes lives on and references the overwritten data.

The only solution I can think of involves copying the data into a new byte slice. Is there away to avoid copying the data?

func pack() []byte {
   ints := []int32{1,2,3,4,5} // This does not escape so it is allocated on the stack
   bytes := intsToBytes(ints) // 'ints' and 'bytes' are different slice headers
   return bytes 
   // After the return, the []int32{...} is deallocated and can be overwritten
   // by the next function's stack data
}

func intsToBytes(i []int32) []byte {
    const SizeOfInt32 = 4

    // Get the slice header
    header := *(*reflect.SliceHeader)(unsafe.Pointer(&i))
    header.Len *= SizeOfInt32
    header.Cap *= SizeOfInt32

    // Convert slice header to an []byte
    data := *(*[]byte)(unsafe.Pointer(&header))

    /* Potentital Solution
    outData := make([]byte, len(data))
    copy(outData, data)
    return outData
    */

    return data
}






Aucun commentaire:

Enregistrer un commentaire