Ian Lance Taylor ec0ebc2281 cmd/gc: treat non-local vars inlined into wrapper as escaping ... The compiler has a phase ordering problem. Escape analysis runs before wrapper generation. When a generated wrapper calls a method defined in a different package, if that call is inlined, there will be no escape information for the variables defined in the inlined call. Those variables will be placed on the stack, which fails if they actually do escape. There are probably various complex ways to fix this. This is a simple way to avoid it: when a generated wrapper calls a method defined in a different package, treat all local variables as escaping. Fixes #9537. Change-Id: I530f39346de16ad173371c6c3f69cc189351a4e9 Reviewed-on: https://go-review.googlesource.com/3092 Reviewed-by: Russ Cox <rsc@golang.org>		2015-01-22 03:25:12 +00:00
..
a.go	cmd/gc: treat non-local vars inlined into wrapper as escaping	2015-01-22 03:25:12 +00:00
b.go	cmd/gc: treat non-local vars inlined into wrapper as escaping	2015-01-22 03:25:12 +00:00