https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96388
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Martin Liška from comment #5) > Started with r9-2469-gc6067437d314f803. Hmm, it probably makes a latent scheduler issue appear. Guess for better analysis we have to trim down the source. Not sure how - maybe automatically with one good and one bad rev. looking for a hundred-fold increase in memory use? Look at the good compile with /usr/bin/time and using the RSS to compute a ulimit -v limit or so.
