https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112408
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #3 from ibuclaw at gcc dot gnu.org --- > Based on what I see here, this patch to core.cpuid should be sufficient to fix > loop and not introduce any change in existing behaviour. I've now bootstrapped a patched gcc 13.2.0 both inside the kernel zone (amd64-pc-solaris2.11) and out, and indeed the build completes and there are no differences in testsuite results between that run and an equivalent one on bare metal. One caveat, though: I originally used an unpatched gcc 11.4.0 as build compiler. However, that doesn't work because the stage 1 d21 is linked with the build compiler's libgphobos, thus loops when used. Applying the patch to the gcc 11.4.0 sources and rebuilding fixed that. Thanks a lot.