aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorIan Lance Taylor <ian@gcc.gnu.org>2018-01-10 05:26:29 +0000
committerIan Lance Taylor <ian@gcc.gnu.org>2018-01-10 05:26:29 +0000
commit692aefcd5618a00e622a1c96957d943723040b4c (patch)
treeae7606fee60c2a35f1f871e4356eb9e02c1b4078 /gcc
parente4876be5f5c5524ea742527100e36c5095181b28 (diff)
downloadgcc-692aefcd5618a00e622a1c96957d943723040b4c.zip
gcc-692aefcd5618a00e622a1c96957d943723040b4c.tar.gz
gcc-692aefcd5618a00e622a1c96957d943723040b4c.tar.bz2
runtime: work around escaping closure in export_test.go
When compiling runtime, it is not allowed for local variables and closures to be heap allocated. In one test, there is a go statement with a closure. In the gc compiler, it distinguishes capturing variable by value vs. by address, and rewrites it to passing the captured values as arguments. Currently we don't have this, and the escape analysis decides to heap allocate the closure and also the captured variables, which is not allowed. Work around it by passing the variables explicitly. This is in preparation of turning on escape analysis for the runtime. Reviewed-on: https://go-review.googlesource.com/86245 From-SVN: r256419
Diffstat (limited to 'gcc')
-rw-r--r--gcc/go/gofrontend/MERGE2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE
index 4404ee2..18c23cf 100644
--- a/gcc/go/gofrontend/MERGE
+++ b/gcc/go/gofrontend/MERGE
@@ -1,4 +1,4 @@
-5cae6a4e0849a3586ee7ce9c915c1520a17db982
+c18c6bd80e0995827ad3396eb1c2401451de88fd
The first line of this file holds the git revision number of the last
merge done from the gofrontend repository.