On Sun, Jun 13, 2021 at 09:16:53PM -0700, Sarah Morgensen via Guix-patches via wrote: > The primary goal for adding gccgo is to bootstrap the go compiler for arches > that aren't supported by go 1.4. I believe the major one to support here is > powerpc64le, but I am unsure of current arch usage. A secondary goal is to > provide a gccgo-toolchain, as gccgo may provide advantages over gc in time. > > I have successfully built gccgo 9, 10 and 11 for x86-64. I additionally tested > gcc 10 using `make check-go`. There are two minor test failures: > > 1. index0-out.go, previously reported upstream [0] > 2. pprof (TestConvertCPUProfile/TestConvertMemProfile) > > (I have not yet been able to deterine whether the pprof failures are an upstream > bug or a Guix bug. Should I send details to bug-guix?) I wouldn't worry about the test failures. > Finally, the regex update in [1] is implemented in CUSTOM-GCC-GCCGO rather than > CUSTOM-GCC to avoid rebuilding 2k+ gfortran packages, and CUSTOM-GCC-GCCGO > should be removed after the change is in master. Makes sense > [0] https://issues.guix.gnu.org/49010 > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87589 > > Sarah Morgensen (1): > gnu: Add gccgo-10. > > gnu/packages/gcc.scm | 77 ++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 77 insertions(+) > > -- > 2.31.1 > I threw together a quick gccgo-toolchain package and tried using that to build keybase and syncthing. One of the errors I came across was: /home/efraim/go/pkg/mod/golang.org/x/sys@v0.0.0-20200922070232-aee5d888a860/unix/gccgo.go:50: undefined reference to `gccgoRealSyscallNoError' and also github.com/minio/sha256-simd@v0.1.1 didn't like the assembly in the package. It's definitely possible that I'm missing some flag to tell go that I'm really using gccgo. Or that it should be built with binutils-gold. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted