function: Do the CLEANUP_EXPENSIVE after shrink-wrapping, not before
commite80af4553ce82e6167c27e58b926a8da70ac3d50
authorsegher <segher@138bc75d-0d04-0410-961f-82ee72b054a4>
Wed, 18 May 2016 10:58:57 +0000 (18 10:58 +0000)
committersegher <segher@138bc75d-0d04-0410-961f-82ee72b054a4>
Wed, 18 May 2016 10:58:57 +0000 (18 10:58 +0000)
tree2209c8792eab859e724568eab2cb9271ef198026
parentb41fcb56cb6075698c4929a75e01f443ebccc206
function: Do the CLEANUP_EXPENSIVE after shrink-wrapping, not before

We should do CLEANUP_EXPENSIVE after shrink-wrapping, because shrink-
wrapping creates constructs that CLEANUP_EXPENSIVE can optimise, and
nothing runs CLEANUP_EXPENSIVE later.

* function.c (rest_of_handle_thread_prologue_and_epilogue): Call
cleanup_cfg with CLEANUP_EXPENSIVE after shrink-wrapping instead
of before.  Add a comment.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@236372 138bc75d-0d04-0410-961f-82ee72b054a4
gcc/ChangeLog
gcc/function.c