libgo: If compiler can split-stack and linker can not, use -fno-split-stack.
authorIan Lance Taylor <ian@gcc.gnu.org>
Tue, 15 Sep 2015 21:15:37 +0000 (21:15 +0000)
committerIan Lance Taylor <ian@gcc.gnu.org>
Tue, 15 Sep 2015 21:15:37 +0000 (21:15 +0000)
commita2bf11d16a01ced5d2bd0500a6896627b7bed076
treecc1561d9c684e30e43f7804a87ab7caab0047110
parentc8338173d725ca0690f25f54e04171ed6cad6be9
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
libgo/Makefile.am
libgo/Makefile.in
libgo/configure
libgo/configure.ac
libgo/testsuite/Makefile.in