Re: [gofrontend-dev] Go patch committed: avoid allocation of varargs parameter with optimize-allocs

2016-10-06 Thread Ian Lance Taylor
On Thu, Oct 6, 2016 at 9:35 AM, Chris Manghane wrote: > > I noticed that this patch does not include the change go-gcc.cc that caused > stack-allocated memory to be incorrectly initialized. Can you add this patch > as well? Whoops, sorry for missing that. Committed with the appended ChangeLog en

Go patch committed: avoid allocation of varargs parameter with optimize-allocs

2016-10-05 Thread Ian Lance Taylor
This patch by Chris Manghane fixes a bug in the escape analysis pass of the Go frontend. The slice created to hold the values passed to a varargs parameter would always escape. This also fixes a bug in which a stack-allocated varargs parameter was incorrectly initialized in some cases. Bootstrap