https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114426
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- As a band-aid, can we turn the gcc_assert into a gcc_checking_assert to make the issue latent (again) on release branches? I understand the issue _is_ latent?