https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103393
--- Comment #13 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
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.
