On Fri, 4 Feb 2022, Richard Sandiford wrote:
> Richard Biener writes:
> > On Fri, 4 Feb 2022, Richard Sandiford wrote:
> >> Richard Biener via Gcc-patches writes:
> >> > niter analysis uses multiple_of_p which currently assumes
> >> > operations like MULT_EXPR do not wrap. We've got to rely on
Richard Biener writes:
> On Fri, 4 Feb 2022, Richard Sandiford wrote:
>> Richard Biener via Gcc-patches writes:
>> > niter analysis uses multiple_of_p which currently assumes
>> > operations like MULT_EXPR do not wrap. We've got to rely on this
>> > for optimizing size expressions like those in
On Fri, 4 Feb 2022, Richard Sandiford wrote:
> Richard Biener via Gcc-patches writes:
> > niter analysis uses multiple_of_p which currently assumes
> > operations like MULT_EXPR do not wrap. We've got to rely on this
> > for optimizing size expressions like those in DECL_SIZE and those
> > gener
Richard Biener via Gcc-patches writes:
> niter analysis uses multiple_of_p which currently assumes
> operations like MULT_EXPR do not wrap. We've got to rely on this
> for optimizing size expressions like those in DECL_SIZE and those
> generally use unsigned arithmetic with no indication that the
niter analysis uses multiple_of_p which currently assumes
operations like MULT_EXPR do not wrap. We've got to rely on this
for optimizing size expressions like those in DECL_SIZE and those
generally use unsigned arithmetic with no indication that they
are not expected to wrap. To preserve that th
