aboutsummaryrefslogtreecommitdiff
path: root/gcc/ira.c
diff options
context:
space:
mode:
authorSteven Bosscher <steven@gcc.gnu.org>2012-10-13 13:21:34 +0000
committerSteven Bosscher <steven@gcc.gnu.org>2012-10-13 13:21:34 +0000
commit544e7e783525054b1e4831e2fc001a18b67c6cbf (patch)
tree645ddc683c9b0c8877caa17c71dce5e3a9122af7 /gcc/ira.c
parent5440a1b0fe1122a2e044023c9c7508d9205bfa14 (diff)
downloadgcc-544e7e783525054b1e4831e2fc001a18b67c6cbf.zip
gcc-544e7e783525054b1e4831e2fc001a18b67c6cbf.tar.gz
gcc-544e7e783525054b1e4831e2fc001a18b67c6cbf.tar.bz2
ira.c (ira): Set current_loops to &ira_loops before recording loop exits.
* ira.c (ira): Set current_loops to &ira_loops before recording loop exits. Release recorded exits and loops early. From-SVN: r192423
Diffstat (limited to 'gcc/ira.c')
-rw-r--r--gcc/ira.c10
1 files changed, 8 insertions, 2 deletions
diff --git a/gcc/ira.c b/gcc/ira.c
index 4a7dcb5..9a93297 100644
--- a/gcc/ira.c
+++ b/gcc/ira.c
@@ -4233,8 +4233,8 @@ ira (FILE *f)
if (flag_ira_region == IRA_REGION_ALL || flag_ira_region == IRA_REGION_MIXED)
{
flow_loops_find (&ira_loops);
- record_loop_exits ();
current_loops = &ira_loops;
+ record_loop_exits ();
}
if (internal_flag_ira_verbose > 0 && ira_dump_file != NULL)
@@ -4277,9 +4277,14 @@ ira (FILE *f)
info. */
df_analyze ();
+ /* ??? Rebuild the loop tree, but why? Does the loop tree
+ change if new insns were generated? Can that be handled
+ by updating the loop tree incrementally? */
+ release_recorded_exits ();
+ flow_loops_free (&ira_loops);
flow_loops_find (&ira_loops);
- record_loop_exits ();
current_loops = &ira_loops;
+ record_loop_exits ();
setup_allocno_assignment_flags ();
ira_initiate_assign ();
@@ -4363,6 +4368,7 @@ do_reload (void)
if (current_loops != NULL)
{
+ release_recorded_exits ();
flow_loops_free (&ira_loops);
free_dominance_info (CDI_DOMINATORS);
}