https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111249
--- Comment #5 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Sam James from comment #3) > (In reply to Sam James from comment #2) > > Bisecting from 11 (good) -> 12 (bad) gave r12-4871-g502ffb1f389011 as the > > breaking commit. > > > > Bisecting from 13 (bad) -> 14 (good) gave r14-2926-gee20be8325f7f2 as the > > fix commit. > > sorry I mean r14-2927-g399c8dd44ff44f for the last one But unless the heuristic was wrong, that means it's latent now and needs more analysis.