https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65233
--- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- FWIW, I also ran valgrind on cc1plus just for good measure, to see if we were hitting some uninitialized memory issues, but I came out empty handed: reynosa:/dev/shm/t/gcc$ valgrind --leak-check=no --track-origins=yes ./cc1plus a.c -quiet -O3 -I./ ==16433== Memcheck, a memory error detector ==16433== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==16433== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==16433== Command: ./cc1plus a.c -quiet -O3 -I./ ==16433== ==16433== ==16433== HEAP SUMMARY: ==16433== in use at exit: 604,299 bytes in 3,095 blocks ==16433== total heap usage: 45,429 allocs, 42,334 frees, 26,667,821 bytes allocated ==16433== ==16433== For a detailed leak analysis, rerun with: --leak-check=full ==16433== ==16433== For counts of detected and suppressed errors, rerun with: -v ==16433== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) p.s. I disabled the memory leak checks because I found a handful of them, most of which were expected or minor enough to be irrelevant.
