The traversal used by the write barrier insertion phase can sometimes
wind up visiting new statements inserted during the traversal, which
then results in duplicate / redundant write barrier guards. Example
program to reproduce:
package small
type S struct {
N *S
K int
}
var G *S = &S{N: nil, K: 101}
This patch changes the traversal code to keep track of statements
already added and avoid processing them again later in the traversal.
Fixes golang/go#25867
Reviewed-on: https://go-review.googlesource.com/118637
From-SVN: r261568
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| gofrontend | Loading commit data... | |
| ChangeLog | Loading commit data... | |
| Make-lang.in | Loading commit data... | |
| README.gcc | Loading commit data... | |
| config-lang.in | Loading commit data... | |
| gccgo.texi | Loading commit data... | |
| go-backend.c | Loading commit data... | |
| go-c.h | Loading commit data... | |
| go-gcc-diagnostics.cc | Loading commit data... | |
| go-gcc.cc | Loading commit data... | |
| go-gcc.h | Loading commit data... | |
| go-lang.c | Loading commit data... | |
| go-linemap.cc | Loading commit data... | |
| go-location.h | Loading commit data... | |
| go-sha1.cc | Loading commit data... | |
| go-system.h | Loading commit data... | |
| gospec.c | Loading commit data... | |
| lang-specs.h | Loading commit data... | |
| lang.opt | Loading commit data... |