https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121777
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Basil Milanich from comment #6) > > What about Godbolt's trunk, is this the same bug - Godbolt does not report > --enable-checking in its config but this could be forced in the source? The developmental GCC trunk defaults to --enable-checking=yes if not supplied a --enable-checking option. While releases branches default to --enable-checking=release. Hope that helps understand why it ICEs on the trunk (on godbolt without a --enable-checking option supplied). Also godbolt has some released compilers built with --enable-checking=yes (named `x86_64 gcc VERS (assertions)` where VERS is replaced with a version # like 15.2).
