dongwopu8210 2017-02-15 07:34
浏览 121

Go中关于堆栈分配的什么是“小”对象?

The code:

func MaxSmallSize() {
    a := make([]int64, 8191)
    b := make([]int64, 8192)
    _ = a
    _ = b
}

Then run go build -gcflags='-m' . 2>&1 to check memory allocation details. The result:

./mem.go:10: can inline MaxSmallSize
./mem.go:12: make([]int64, 8192) escapes to heap
./mem.go:11: MaxSmallSize make([]int64, 8191) does not escape

My question is why a is small object and b is large object?

make 64KB will escape to heap and less will allocate in stack. Does the _MaxSmallSize = 32 << 10 is the reason?

go env

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/vagrant/gopath"
GORACE=""
GOROOT="/home/vagrant/go"
GOTOOLDIR="/home/vagrant/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build201775001=/tmp/go-build"
CXX="g++"
CGO_ENABLED="1"
  • 写回答

1条回答 默认 最新

  • douzhan3900 2017-02-15 08:25
    关注

    Since this is not mentioned in the language spec, it is an implementation detail, and as such, it may vary based on a number of things (Go version, target OS, architecture etc.).

    If you want to find out its current value or a place to start digging, check out the cmd/compile/internal/gc package.

    The escape analysis which decides where to allocate the variable is in cmd/compile/internal/gc/esc.go. Check of the make slice operation is in unexported function esc():

    func esc(e *EscState, n *Node, up *Node) {
        // ...
    
        // Big stuff escapes unconditionally
        // "Big" conditions that were scattered around in walk have been gathered here
        if n.Esc != EscHeap && n.Type != nil &&
            (n.Type.Width > MaxStackVarSize ||
                (n.Op == ONEW || n.Op == OPTRLIT) && n.Type.Elem().Width >= 1<<16 ||
                n.Op == OMAKESLICE && !isSmallMakeSlice(n)) {
            if Debug['m'] > 2 {
                Warnl(n.Lineno, "%v is too large for stack", n)
            }
            n.Esc = EscHeap
            addrescapes(n)
            escassignSinkNilWhy(e, n, n, "too large for stack") // TODO category: tooLarge
        }
    
        // ...
    }
    

    The decision involving the size is in function isSmallMakeSlice(), this is in file cmd/compile/internal/gc/walk.go:

    func isSmallMakeSlice(n *Node) bool {
        if n.Op != OMAKESLICE {
            return false
        }
        l := n.Left
        r := n.Right
        if r == nil {
            r = l
        }
        t := n.Type
    
        return Smallintconst(l) && Smallintconst(r) && (t.Elem().Width == 0 || r.Int64() < (1<<16)/t.Elem().Width)
    }
    

    The size limit is this:

    r.Int64() < (1<<16)/t.Elem().Width
    

    r is the length or capacity of the slice (if cap is provided), t.Elem().Width is the byte size of the element type:

    NumElem < 65536 / SizeElem
    

    In your case:

    NumElem < 65536 / 8 = 8192
    

    So if the slice type is []uint64, 8192 is the limit from which it is allocated on the heap (instead of the stack), just as you experienced.

    评论

报告相同问题?

悬赏问题

  • ¥15 yolov8边框坐标
  • ¥15 matlab中使用gurobi时报错
  • ¥15 WPF 大屏看板表格背景图片设置
  • ¥15 这个主板怎么能扩出一两个sata口
  • ¥15 不是,这到底错哪儿了😭
  • ¥15 2020长安杯与连接网探
  • ¥15 关于#matlab#的问题:在模糊控制器中选出线路信息,在simulink中根据线路信息生成速度时间目标曲线(初速度为20m/s,15秒后减为0的速度时间图像)我想问线路信息是什么
  • ¥15 banner广告展示设置多少时间不怎么会消耗用户价值
  • ¥16 mybatis的代理对象无法通过@Autowired装填
  • ¥15 可见光定位matlab仿真