------- Comment #2 from hubicka at gcc dot gnu dot org 2009-06-08 15:54 ------- The loops should be in sync, but I am but confused here.
I originally added the code only when walking types, not actual declarations, since in decls we don't use that VOIDtype terminator. There was some side case where declaration actually had VOID argument in C++, but I don't recall the exact scenario. There is gcc_assert (!VOID_TYPE_P (type)) in estimate_move_cost I would expect to fire if we was ever compiling function having VOID in the parm list. How did you fire the >= 0 assert? Honza -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40223
