https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114821
--- Comment #13 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Thanks a lot, looks great! Do we still auto-detect memmove when the copy constructor turns out to be memcpy equivalent after optimization?
