https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90594
--- Comment #16 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 15 Nov 2024, pinskia at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90594 > > Andrew Pinski <pinskia at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > See Also| |https://gcc.gnu.org/bugzill > | |a/show_bug.cgi?id=117572, > | |https://gcc.gnu.org/bugzill > | |a/show_bug.cgi?id=60412, > | |https://gcc.gnu.org/bugzill > | |a/show_bug.cgi?id=111630 > > --- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > (In reply to Andrew Pinski from comment #14) > > I should note some of the reuse stack issues are due to sccp even though the > > pointer value is there at the end anyways ... > > PR 117572 and PR 60412 and PR 111630 are an examples where the sccp is not > needed because the pointer is already correct at the end of the loop but we do > sccp anyways. The value is always correct at the end of the loop - the idea of SCCP is to a) remove an induction variable, b) eventually allow to elide the loop completely. We check neither - I had a prototype wiring in the thing into DCE, when a LC PHI can be SCCPed, do not mark it necessary.
