https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122863
--- Comment #6 from anlauf at gcc dot gnu.org --- (In reply to Steve Kargl from comment #5) > AFAICT, the above is leaked memory from the array constructor. This was not about the leak. It was about the uninitialized memory reads that happen at -m64. That is one issue. The -m32 strangeness might be a separate issue, and apparently worse.
