https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78618
--- Comment #11 from janus at gcc dot gnu.org --- (In reply to Steve Kargl from comment #10) > Others are see the failures. > > https://gcc.gnu.org/ml/gcc-testresults/2016-12/msg00313.html > https://gcc.gnu.org/ml/gcc-testresults/2016-12/msg00311.html Not sure why I don't see this. Doing a full bootstrap does not seem to help either. > I think your patch is correct, but uncovering a new latent bug. > Does your memory allocator fill freed memory with junk? Not sure. How can I tell? It's kind of hard to debug this without being able to reproduce the problem ...
