diff options
| author | Segher Boessenkool <segher@kernel.crashing.org> | 2016-05-18 12:58:57 +0200 |
|---|---|---|
| committer | Segher Boessenkool <segher@gcc.gnu.org> | 2016-05-18 12:58:57 +0200 |
| commit | 63d0f6ab560336d34b0a8f9b9b111c4a17e8737f (patch) | |
| tree | 2209c8792eab859e724568eab2cb9271ef198026 /gcc/tree-ssa-loop-im.c | |
| parent | a1e71b01801dbf67c2dc9d598b3e62091b4677b2 (diff) | |
| download | gcc-63d0f6ab560336d34b0a8f9b9b111c4a17e8737f.zip gcc-63d0f6ab560336d34b0a8f9b9b111c4a17e8737f.tar.gz gcc-63d0f6ab560336d34b0a8f9b9b111c4a17e8737f.tar.bz2 | |
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.
From-SVN: r236372
Diffstat (limited to 'gcc/tree-ssa-loop-im.c')
0 files changed, 0 insertions, 0 deletions