re #3 solved the GCC stability issue on i5: removed the "debug output" -g option. Alone, -g does not lead to GCC instability, but in combination with at least one of the optimization option, it starts sucking the whole memory. So far, I experienced this on an i5 only (Thinkpad T420s)