https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85720
--- Comment #4 from Mathias Stearn ---
(In reply to Marc Glisse from comment #3)
> Again, you are ignoring aliasing issues (just like in your other PR the
> function copy isn't equivalent to memmove). Does adding __restrict change
> the result?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85720
--- Comment #3 from Marc Glisse ---
(In reply to Mathias Stearn from comment #2)
> Hmm. Taking the example from the -ftree-loop-distribute-patterns
> documentation, it still seems to generate poor code, this time at both -O2
> and -O3:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85720
--- Comment #2 from Mathias Stearn ---
Hmm. Taking the example from the -ftree-loop-distribute-patterns documentation,
it still seems to generate poor code, this time at both -O2 and -O3:
https://godbolt.org/g/EsQDj8
Why isn't that transformed
