Jonathan Perkin

Speaking of GCC, does anyone know of any lawful impediment why I may not drop gccgo from my GCC packages?

Feels like something that hasn't been necessary since 2013.

#illumos #gcc #go

Mar 13, 2024 at 1:20pmWeb
Show threadbenzMar 13, 2024

@jperkin I think it has very little usage. I was looking into supporting #gccgo as an alternative toolchain for #pkgsrc but never got anywhere.

I did get the #NetBSD build of #gccgo fixed though.

Show threadTerin StockMar 13, 2024
@jperkin IIRC it’s still stuck at Go 1.18, and doesn’t support generics. I’m not aware of anyone who uses or tests with it.
Show threadAlan CoopersmithMar 13, 2024
@jperkin we ship gccgo in Solaris because it has a SPARC backend while Google’s go compiler does not, but that shouldn’t matter for illumos (except for the SPARC forks of Tribblix & OpenIndiana).
Show threadJonathan PerkinMar 13, 2024
@alanc yeh that feels like the only reason to use it these days. I've dropped it, which also has the side benefit of reducing the size of my GCC packages from 255MB to 167MB.
Show threadOlaf BohlenMar 13, 2024
@alanc @jperkin oh, good to know…I have some high quality golang code *cough* that I probably need to have on sparc. I wasn’t aware that one could compile that with gcc on sparc