https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68302
--- Comment #20 from Steve Ellcey <sje at gcc dot gnu.org> --- I have still not been able to reproduce this or understand what is happening. Aurelien, could you try applying the patch that has been submitted for PR 69129 to see if that helps? The failure modes for this bug and 69129 don't look the same but I think both may be related to uninitialized memory usage and I can't reproduce either one so I am hoping maybe they have the same root cause. Patch for PR 69129: https://gcc.gnu.org/ml/gcc-patches/2016-01/msg01407.html
