Jim, adding you to the discussion. I was not able to build gold, by configuring binutils, using
> ./configure --enable-gold > did not allow GNU make tool to build gold: many sub-directories were processed, to compile the sources/generate files - but not the sub-dir. for gold. When I entered the "gold" dir. and ran "configure" script - it failed with an error, which reported an unsupported arch. , under qemu. Is there any way to compile gold? Perhaps I have improper identification of the arch.? Perhaps there is a working Makefile, for this (until "configure" would be patched properly)? What about cross-compiling (Linux x86_64 -> Linux 64bit RISC-V ) ? Ivan On Tue, Nov 24, 2020 at 4:20 PM Ian Lance Taylor <i...@golang.org> wrote: > On Tue, Nov 24, 2020 at 6:14 AM Richard W.M. Jones <rjo...@redhat.com> > wrote: > > > > One thing I'm missing: Why does golang need gold? > > The gccgo and GoLLVM compilers (which are not the most widely used Go > compilers) require the gold linker for full support of stack > splitting. Stack splitting is used to ensure that goroutines do not > run out of stack space. Stack splitting is supported by gold and lld, > but, as far as I know, is not supported by the GNU linker. > > However, the bulk of stack splitting support is in the compiler, At > least for GCC, stack splitting is only supported on x86, PPC, and > S/390. So at least until stack splitting support is added for RISC/V, > there is no particular reason to require the gold linker for RISC/V. > > (It does seem a shame that people are thinking of deprecating gold, > but it's certainly true that I have not had time to maintain it.) > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CANFCsz9EdJWL87oX%2BeLrzBbK5m%3DFzwVs6Z8RQ55feJ34v%2BH42Q%40mail.gmail.com.
