[Bug tree-optimization/44563] GCC uses a lot of RAM when compiling a large numbers of functions

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44563

--- Comment #22 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder why we have split_bb_on_noreturn_calls in cfg-cleanup rather than in
fixup_cfg.  It's quite expensive, walking all stmts and calling
gimple_call_noreturn_p which is very expensive.  We fixup noreturn calls in
fixup cfg so I wonder why we have this leftover in cfgcleanup...  testing
removal.