Hi all,
Since BZ#67877 [1] does not have much information on it, I would like
to ask for some inputs of which is the requirement of implementing
split-stack on aarch64 besides 'feature parity'.
I am asking it because on PR it states the main use it gccgo and
afaik there is some usage in other programs, but the widespread
is not really convincing (for instance, rust now allows targets
to be built without it [2]).
I also noted GO from 1.4 does not use split-stack anymore, stating
it suffers from a performance issue ("hot stack split") and some
search on the internet describes that for 64-bit targets split-stack
is not really an efficient way to manage stack grows.
So this is only for gccgo support? It gccgo stuck in pre 1.4 version
and/or not willing remove split-stack usage (as go itself)?
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67877
[2] https://github.com/rust-lang/rust/issues/16980
