------- Comment #9 from rguenth at gcc dot gnu dot org 2010-02-27 22:20 ------- (In reply to comment #8) > > Well, it really only requires much time and memory to compile, > > it's not never ending ;) > > Ah, it means that machine is old. > > Also, the generated code is larger then what gcc 4.3 does (4.4 is affected, > too). Should I file a bug report?
GCC 4.3 did only unroll the very innermost loops. GCC 4.4 does have the same code (so I wondered why your initial testcase didn't trigger) - I can backport the parm change there. As for the size of the code - you can file a bugreport but what the loop optimizer analyzes looks reasonable. So I guess the inliner with its improved size/time estimates inlines more (you might want to verify this). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43186
