[Bug go/92564] libgo regression in runtime test resulting in SIGSEGV on ppc64le

[boger at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92564

--- Comment #3 from boger at gcc dot gnu.org ---
Yes, I tried the value of 0x8 and the test passed. In the issue Ian
mentioned that 0x10 was the default on x86. If we want the same default on
x86 and ppc64 then 0x10 would work since the value I tested with is
smaller.

[Bug go/92564] libgo regression in runtime test resulting in SIGSEGV on ppc64le

[amodra at gmail dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92564

Alan Modra  changed:

   What|Removed |Added

 CC|amodra at gcc dot gnu.org  |

--- Comment #2 from Alan Modra  ---
Did you try Ian's suggestion of -Wl,--split-stack-adjust-size=0x8000 or even
larger?

[Bug go/92564] libgo regression in runtime test resulting in SIGSEGV on ppc64le

[boger at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92564

boger at gcc dot gnu.org changed:

   What|Removed |Added

 CC||amodra at gcc dot gnu.org,
   ||amodra at gmail dot com

--- Comment #1 from boger at gcc dot gnu.org ---
More information on this bug has been added to
https://github.com/golang/go/issues/36697. The problem appears to be due the
use of split stack and possibly the gold linker is not handling the split stack
functions correctly in libgcc generic-morestack.c.