https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80548
--- Comment #9 from Jeffrey A. Law <law at gcc dot gnu.org> --- These warnings are certainly sensitive to all kinds of things, so it's possible it's just gone latent. The only way to be sure would be to bisect all the work between gcc-12 and the trunk and pour over the dumps with a fine tooth comb. I would hazard a guess it was Aldy's backwards threader work, particularly around not bailing out too early for subpaths based on comments in the BZ, but one would have to bisect to be 100% sure. What I would recommend would be opening a new bug for the new cases. While these bugs often appear to be the same, it's actually fairly rare in practice that they have the same underlying cause. Each has to be analysed individually.
