https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101197
--- Comment #7 from cqwrteur <unlvsur at live dot com> --- (In reply to Jakub Jelinek from comment #6) > Shouldn't that be a different PR with details? I mean, this PR is that we > should expand shorter memmove inline even if the regions do overlap. clang also has __builtin_memcpy_inline and __builtin_memmove_inline, __builtin_memset_inline that only accepts constant. Do we need something like that?