http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54632
--- Comment #9 from Zdenek Sojka <zsojka at seznam dot cz> 2012-09-24 09:38:40 UTC --- If I remember correctly, with --param ggc-min-expand=0 --param ggc-min-heapsize=0 the program didn't crash - maybe the space was reallocated of another tree, so the pointer became valid again. I tried to compile gcc with --disable-bootstrap --enable-checking=valgrind, but the compilation fails when linking (saying I should use -fPIC). That would give me the chance to use valgrind to find the invalid memory access (memory allocations aren't hooked by valgrind here; valgrind checking adds explicit calls to valgrind routines). I am not reducing the file any longer, if it's caused by invalid memory references, the crash could appear and disappear 'randomly' with changes in the code.
