https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108846
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #7) > I suspect std::move has the same issue too. The ability to use memmove with > trivial copyable subobjects ... std::move(x,y,z) and std::copy(z,y,z) use the same underlying implementation, so it does have the same issue, but will be fixed by the same change.
