------- Comment #1 from jakub at gcc dot gnu dot org 2009-04-01 08:35 -------
You haven't shown how long did it take in earlier versions, this test is
already known to take eons (and when gimplify.o isn't built with optimizations
even ICE on many targets) and has /* { dg-timeout-factor 4.0 } */ already.
What slows down the test is extremely deep recursion above 22000-33000 calls in
the backtrace (for each ONE either just gimplify_expr and gimplify_cond_expr,
or even gimplify_stmt in the backtrace). Even a small RA decision affecting
these functions can show up when multiplied by 11000, but the testcase is
clearly artificial and not worth optimizing for.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38059
