https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112868
--- Comment #16 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Peter Bergner from comment #14) > (In reply to Niels Möller from comment #13) > > I'm not that familiar with gcc development procedures. Do I understand you > > correctly, that a fix for this bug will not be included in gcc-14 (according > > to https://gcc.gnu.org/develop.html#timeline, gcc-14 stage1 ended several > > months ago), it will have to wait for gcc-15? > > Correct, I meant waiting for GCC 15 stage1. I want it to burn-in on trunk > for a long while, because it had the potential to disrupt distro package > builds. It seems clean so far with the practice Gentoo builds, but I'll > feel more comfortable when other distros start using it too. FWIW, we're keeping it going forward (so it'll be in e.g. our GCC 14 patchset when we unleash that on the masses). Just keep in mind that very few distributions build with > release checking. We only do default-checking for the branch when it's in development still and also optionally via USE=debug. So, while testing by others is still valuable, I don't expect you'll get that much - at least without people specifically knowing to turn on checking and ensure stuff doesn't break. (Of course, making sure release checking works fine now too is important, but you get my point.)
