From a2bf11d16a01ced5d2bd0500a6896627b7bed076 Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Tue, 15 Sep 2015 21:15:37 +0000 Subject: libgo: If compiler can split-stack and linker can not, use -fno-split-stack. If the compiler supports split-stack but we are using a gold linker that does not, as happens on PPC with current GCC but old gold, then we need to compile the Go code with -fno-split-stack to avoid a linker error avoid the inability to call from split-stack code to non-split-stack code. Reviewed-on: https://go-review.googlesource.com/14598 From-SVN: r227811 --- gcc/go/gofrontend/MERGE | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gcc') diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index b1a7895..21458cd 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -6f0ac34e139755c319368757fe2a093f1e5bde49 +eac8b31fec761c8da0606a70ae0547ff0b12e8db The first line of this file holds the git revision number of the last merge done from the gofrontend repository. -- cgit v1.1