https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90471
--- Comment #13 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to Richard Biener from comment #12) > The valgrind log isn't very useful unless you configure GCC with > --enable-valgrind-annotations > > The segfault might hint at stack exhaustion (at least I don't see > a freed GC object being walked). What is the stack size limit on > mingw and can you increase it? I have a reduced test-case of about 50k. It happens for a cross compiler and we would see a stack overflow in valgrind.
