------- Comment #5 from matz at gcc dot gnu dot org 2010-04-08 13:40 ------- Um, how can r138953 be the reason when (as the original report says) it's still okay with r153685? In any case, my patch just shuffled around the activation/non-activation of the scheduler, so if at all it exposed a latent bug in it, which given that -fsched2-use-superblocks isn't used by default is very likely.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43671
