mirror of
https://github.com/golang/go
synced 2024-11-18 09:24:54 -07:00
6722d45631
1. On entry to a function, only zero the ambiguously live stack variables. Before, we were zeroing all stack variables containing pointers. The zeroing is pretty inefficient right now (issue 7624), but there are also too many stack variables detected as ambiguously live (issue 7345), and that must be addressed before deciding how to improve the zeroing code. (Changes in 5g/ggen.c, 6g/ggen.c, 8g/ggen.c, gc/pgen.c) Fixes #7647. 2. Make the regopt word-based liveness analysis preserve the whole-variable liveness property expected by the garbage collection bitmap liveness analysis. That is, if the regopt liveness decides that one word in a struct needs to be preserved, make sure it preserves the entire struct. This is particularly important for multiword values such as strings, slices, and interfaces, in which all the words need to be present in order to understand the meaning. (Changes in 5g/reg.c, 6g/reg.c, 8g/reg.c.) Fixes #7591. 3. Make the regopt word-based liveness analysis treat a variable as having its address taken - which makes it preserved across all future calls - whenever n->addrtaken is set, for consistency with the gc bitmap liveness analysis, even if there is no machine instruction actually taking the address. In this case n->addrtaken is incorrect (a nicer way to put it is overconservative), and ideally there would be no such cases, but they can happen and the two analyses need to agree. (Changes in 5g/reg.c, 6g/reg.c, 8g/reg.c; test in bug484.go.) Fixes crashes found by turning off "zero everything" in step 1. 4. Remove spurious VARDEF annotations. As the comment in gc/pgen.c explains, the VARDEF must immediately precede the initialization. It cannot be too early, and it cannot be too late. In particular, if a function call sits between the VARDEF and the actual machine instructions doing the initialization, the variable will be treated as live during that function call even though it is uninitialized, leading to problems. (Changes in gc/gen.c; test in live.go.) Fixes crashes found by turning off "zero everything" in step 1. 5. Do not treat loading the address of a wide value as a signal that the value must be initialized. Instead depend on the existence of a VARDEF or the first actual read/write of a word in the value. If the load is in order to pass the address to a function that does the actual initialization, treating the load as an implicit VARDEF causes the same problems as described in step 4. The alternative is to arrange to zero every such value before passing it to the real initialization function, but this is a much easier and more efficient change. (Changes in gc/plive.c.) Fixes crashes found by turning off "zero everything" in step 1. 6. Treat wide input parameters with their address taken as initialized on entry to the function. Otherwise they look "ambiguously live" and we will try to emit code to zero them. (Changes in gc/plive.c.) Fixes crashes found by turning off "zero everything" in step 1. 7. An array of length 0 has no pointers, even if the element type does. Without this change, the zeroing code complains when asked to clear a 0-length array. (Changes in gc/reflect.c.) LGTM=khr R=khr CC=golang-codereviews https://golang.org/cl/80160044
91 lines
1.8 KiB
Go
91 lines
1.8 KiB
Go
// run
|
|
|
|
// Copyright 2014 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.
|
|
|
|
// The liveness code used to say that, in func g, s was live
|
|
// starting at its declaration, because it appears to have its
|
|
// address taken by the closure (different s, but the parser
|
|
// gets slightly confused, a separate bug). The liveness analysis
|
|
// saw s as having its address taken but the register optimizer
|
|
// did not. This mismatch meant that s would be marked live
|
|
// (and therefore initialized) at the call to f, but the register optimizer
|
|
// would optimize away the initialization of s before f, causing the
|
|
// garbage collector to use unused data.
|
|
// The register optimizer has been changed to respect the
|
|
// same "address taken" flag that the liveness analysis uses,
|
|
// even if it cannot see any address being taken in the actual
|
|
// machine code. This is conservative but keeps the two consistent,
|
|
// which is the most important thing.
|
|
|
|
package main
|
|
|
|
import "runtime"
|
|
|
|
var c bool
|
|
|
|
func f() interface{} {
|
|
if c { // disable inlining
|
|
f()
|
|
}
|
|
runtime.GC()
|
|
return nil
|
|
}
|
|
|
|
func g() {
|
|
if c { // disable inlining
|
|
g()
|
|
}
|
|
var s interface{}
|
|
_ = func() {
|
|
s := f()
|
|
_ = s
|
|
}
|
|
s = f()
|
|
useiface(s)
|
|
useiface(s)
|
|
}
|
|
|
|
func useiface(x interface{}) {
|
|
if c { // disable inlining
|
|
useiface(x)
|
|
}
|
|
}
|
|
|
|
func h() {
|
|
if c { // disable inlining
|
|
h()
|
|
}
|
|
var x [16]uintptr
|
|
for i := range x {
|
|
x[i] = 1
|
|
}
|
|
|
|
useint(x[0])
|
|
useint(x[1])
|
|
useint(x[2])
|
|
useint(x[3])
|
|
}
|
|
|
|
func useint(x uintptr) {
|
|
if c { // disable inlining
|
|
useint(x)
|
|
}
|
|
}
|
|
|
|
func main() {
|
|
// scribble non-zero values on stack
|
|
h()
|
|
// call function that used to let the garbage collector
|
|
// see uninitialized stack values; it will see the
|
|
// nonzero values.
|
|
g()
|
|
}
|
|
|
|
func big(x int) {
|
|
if x >= 0 {
|
|
big(x-1)
|
|
}
|
|
}
|