1
0
mirror of https://github.com/golang/go synced 2024-11-13 12:50:44 -07:00
go/test/fixedbugs/issue67255.go
Keith Randall 93e3696b5d cmd/compile: avoid past-the-end pointer when zeroing
When we optimize append(s, make([]T, n)...), we have to be careful
not to pass &s[0] + len(s)*sizeof(T) as the argument to memclr, as that
pointer might be past-the-end. This can only happen if n is zero, so
just special-case n==0 in the generated code.

Fixes #67255

Change-Id: Ic680711bb8c38440eba5e759363ef65f5945658b
Reviewed-on: https://go-review.googlesource.com/c/go/+/584116
Reviewed-by: Austin Clements <austin@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Cuong Manh Le <cuong.manhle.vn@gmail.com>
Reviewed-by: Keith Randall <khr@google.com>
2024-05-08 17:09:06 +00:00

34 lines
922 B
Go

// run
// Copyright 2024 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
package main
var zero int
var sink any
func main() {
var objs [][]*byte
for i := 10; i < 200; i++ {
// The objects we're allocating here are pointer-ful. Some will
// max out their size class, which are the ones we want.
// We also allocate from small to large, so that the object which
// maxes out its size class is the last one allocated in that class.
// This allocation pattern leaves the next object in the class
// unallocated, which we need to reproduce the bug.
objs = append(objs, make([]*byte, i))
}
sink = objs // force heap allocation
// Bug will happen as soon as the write barrier turns on.
for range 10000 {
sink = make([]*byte, 1024)
for _, s := range objs {
s = append(s, make([]*byte, zero)...)
}
}
}