https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #19 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 24 May 2023, userm57 at yahoo dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927 > > --- Comment #18 from Stan Johnson <userm57 at yahoo dot com> --- > $ git clone git://gcc.gnu.org/git/gcc.git > $ cd gcc > $ git checkout master > > I'm testing a manual bootstrap of "gcc version 14.0.0 20230524 (experimental) > (GCC)" now, accessed via git as shown above. > > It will still take about 24 more hours for the bootstrap to finish (I'll send > an update if it fails), but with gimple-match.cc (and generic-match.cc, which > was not affected in my tests) split up, it looks like it will finish ok (it's > currently in about the middle of stage 2 and has successfully compiled all the > gimple-match-n.cc files). > > Note that Gentoo's emerge of gcc-13 behaves a little differently than a manual > bootstrap. I don't know why, since I think I'm using Gentoo's ./configure > options in the manual bootstrap, but in Gentoo's emerge of gcc, they seem to > run cc1plus and "as" simultaneously for each compilation, perhaps aggravating > the memory issue for gimple-match.cc (or maybe not, since the problem is > virtual memory exhausted, not swap space exhausted). Possibly -pipe is used somehow. > Anyway, it looks like the solution was already close. Does anyone know whether > the change will be backported to gcc-12 or gcc-13 available from > ftp.gnu.org/pub/gnu/gcc? That wasn't planned. It's very unlikely to happen for gcc 12, it should be possible for gcc 13 I think.
