[gentoo-dev] What happened to gcc-12.3.0?

[Joshua Kinard <kumba@gentoo.org>]

Noticing that the ebuild for gcc-12.3.0 got dropped with little explanation.  It is the upstream stable 
release.  I am eyeballing #906310 as what may have triggered the drop, but I find it a bit of a stretch that 
an upstream stable release got dropped over a single, optional package that has a history of quirky behavior 
(FWIW, I never had luck with ccache, especially on MIPS).

I know we have the pYYYMMDD ebuilds, but I've been keeping my mips chroots on only the upstream/stable 
releases to minimize the number of times I have to rebuild the compiler, since we make frequent pYYYYMMDD 
releases (once a month, on average, judging by the datestamps), and most of the patches in the pYYYYMMDD 
series don't help or hinder MIPS.

Under qemu, it takes about 4 hours to build the single-ABI variant of gcc and 7 hours for the multilib 
variant.  So I avoid rebuilding the compiler as much as possible, as with six chroots, that's virtually an 
entire day across all six just for gcc, minus distractions (seriously, the build times on gcc are getting 
waaaaaaay out of hand, regardless of arch).

Options?  I mean, if anyone knows magic to make gcc build faster, I am all ears, but ever since the switch to 
C++, the time needed for it to build itself has just been absolutely horrendous.  And it gets worse with each 
new release, for some reason.

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us.  And our lives slip away, moment by 
moment, lost in that vast, terrible in-between."

         --Emperor Turhan, Centauri Republic