https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102844
--- Comment #26 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to Richard Biener from comment #25) > I'm not sure about the state of this bug - the issue reproduces on the GCC > 10 branch with checking enabled and -O[2s] -fdisable-tree-fre4 > -fno-strict-overflow > > It might be that using the backward threader from DOM (are we now doing > that?) > makes this truly fixed but I'm not sure the backward threader is resilent > to the issue analyzed in comments #13 to #15. Eventually the NOCOPY No. DOM is the only remaining use of the forward threader. It does not use the backward threader, nor the ranger path solver.
