On Sun, May 4, 2025 at 11:51 PM Richard Biener
wrote:
>
> On Mon, May 5, 2025 at 3:42 AM Andrew Pinski wrote:
> >
> > While fixing up how rewrite_to_defined_overflow works,
> > gcc.dg/Wrestrict-22.c started
> > to fail. This is because `d p+ 2` would moved by LIM and then be rewritten
> > not u
On Mon, May 5, 2025 at 3:42 AM Andrew Pinski wrote:
>
> While fixing up how rewrite_to_defined_overflow works, gcc.dg/Wrestrict-22.c
> started
> to fail. This is because `d p+ 2` would moved by LIM and then be rewritten
> not using
> pointer plus. The rewriting part is correct behavior. It only
While fixing up how rewrite_to_defined_overflow works, gcc.dg/Wrestrict-22.c
started
to fail. This is because `d p+ 2` would moved by LIM and then be rewritten not
using
pointer plus. The rewriting part is correct behavior. It only recently started
to be
moved out; due to r16-190-g6901d56fea2132
