[Bug tree-optimization/88440] size optimization of memcpy-like code

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88440

--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
> 
> Can you share -fopt-report-loop differences?  From the above I would
> guess we split a lot of loops, meaning the memcpy/memmove/memset
> calls are in the "middle" and we have to split loops (how many
> calls are detected here?).  If that's true another way would be
> to only allow calls at head or tail position, thus a single
> non-builtin partition.

I newly see ~1400 lines:

module_configure.fppized.f90:7993:0: optimized: Loop 10 distributed: split to 0
loops and 1 library calls.
module_configure.fppized.f90:7995:0: optimized: Loop 11 distributed: split to 0
loops and 1 library calls.
module_configure.fppized.f90:8000:0: optimized: Loop 15 distributed: split to 0
loops and 1 library calls.
module_configure.fppized.f90:8381:0: optimized: Loop 77 distributed: split to 0
loops and 1 library calls.
module_configure.fppized.f90:8383:0: optimized: Loop 78 distributed: split to 0
loops and 1 library calls.
module_configure.fppized.f90:8498:0: optimized: Loop 105 distributed: split to
0 loops and 1 library calls.
module_configure.fppized.f90:9742:0: optimized: Loop 169 distributed: split to
0 loops and 1 library calls.
module_configure.fppized.f90:9978:0: optimized: Loop 207 distributed: split to
0 loops and 1 library calls.
module_configure.fppized.f90:9979:0: optimized: Loop 208 distributed: split to
0 loops and 1 library calls.
module_configure.fppized.f90:9980:0: optimized: Loop 209 distributed: split to
0 loops and 1 library calls.
module_configure.fppized.f90:9981:0: optimized: Loop 210 distributed: split to
0 loops and 1 library calls.
...