http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51529
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-12-14 11:18:21 UTC --- (In reply to comment #3) > The memset came about for similar reasons with class objects with > allocatable components. I had missed this wrinkle with the testcase. > My inclination is to restire the memset and keep the PR open. I am fine with it, but state in the comment above the memset that it is needed as _copy tries to free the allocatable components of "dest" - that makes clear why the memset is need for our implementation.