------- Comment #32 from steven at gcc dot gnu dot org 2008-01-08 13:08 ------- You are of course right that for this test case the bigger win is in the algorithmic issues.
On the other hand, for compile time in general, the gcc_asserts are IMHO the worst thing that happened to GCC since the introduction of the garbage allocator ;-) It is way too easy to write "gcc_assert (blah)" instead of "if (blah)\nabort ();", and people don't realize how expensive these "cheap" asserts are. This would then be a nice project for the Wiki beginners projects pages, perhaps: Audit the gcc_assert calls in small "inline" functions and see if there is any measurable gain to win from removing some that don't make sense (like e.g. the ones you identified in comment #30). But that's not relevant for this bug report, of course :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34683
