------- Comment #19 from matz at gcc dot gnu dot org 2010-04-08 14:50 ------- This seems rather like a hack for our not-so-capable loop unroller. The estimator already correctly knows that much of it will be optimized away, hence it would make more sense for the code emitter to also not emit useless things that the estimator already knows will be optimized away.
It seems backward to have an additional limit on "compile time/memory need" for a transformation that we know will succeed. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43186
