Recently the split stack support was added upstream in gccgo for ppc64le.
This causes the split stack flag to be enabled by default in gccgo, and as
a result, the libgo that is built based on USING_SPLIT_STACK being defined,
which enables all the split stack specific code in libgo, as well as
building all other code in libgo with the -fsplit-stack option.
What happens if someone builds using gccgo and the split-stack version of
libgo but sets the -fno-split-stack flag? Is this an issue? Should there
be two versions of libgo built, or is it OK to use this libgo with
I would also like some detail as to when the gold linker is really needed.
In this document https://gcc.gnu.org/wiki/SplitStacks it says you need the
gold linker for full functionality, but there are no details as to what
that means. I see the LINKER_SUPPORTS_SPLIT_STACK define within libgo
affecting the amount of storage allocated for the stack for each goroutine
but that is a gccgo build time attribute and not necessarily what is
available where the gccgo is installed and used.
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.