------- Comment #15 from rguenth at gcc dot gnu dot org 2010-04-08 13:19 ------- (In reply to comment #14) > Adding a simple limit on number of loop nests in recursive inlining is easy > thing to do, but I am not quite sure how useful it is (well, overall recursive > inlining tends to help only few very special benchmrks). > So the problem is that function body after inlinng is resonable but with > unrolling it explodes?
The main issue is that we are doing a very poor job in limiting the work we do during complete unrolling (as well as leaving as little work for subsequent passes as possible). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43186