https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103393
--- Comment #14 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Earnshaw from comment #13)
> Also, note that the comment in gimple-fold.c prior to this change read:
>
> /* If we can perform the copy efficiently with first doing all loads
> and then all stores inline it that way. Currently efficiently
> means that we can load all the memory into a single integer
> register which is what MOVE_MAX gives us. */
>
> Which would imply that the AArch64 definition of MOVE_MAX is the correct one.
The GCC manual has
- Macro: MOVE_MAX
The maximum number of bytes that a single instruction can move
quickly between memory and registers or between two memory
locations.
