> We should do CLEANUP_EXPENSIVE after shrink-wrapping, because shrink- > wrapping creates constructs that CLEANUP_EXPENSIVE can optimise, and > nothing runs CLEANUP_EXPENSIVE later. We don't need cleanup_cfg before > shrink-wrapping, nothing in shrink-wrapping (or the other *logue insertion > code) cares at all.
Are you sure of that? I agree that CLEANUP_EXPENSIVE might be overkill, but can't cleanup_cfg expose more opportunities to have multiple epilogues? -- Eric Botcazou
