[gcc(refs/users/aldyh/heads/threader-refactor)] wip wip
Aldy Hernandez
aldyh@gcc.gnu.org
Wed Nov 25 14:49:21 GMT 2020
https://gcc.gnu.org/g:a68640a8f9f09cce8280233fea43750ceedd9b62
commit a68640a8f9f09cce8280233fea43750ceedd9b62
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Mon Nov 23 18:09:00 2020 +0100
wip wip
BOOTSTRAPS
Diff:
---
gcc/tree-ssa-threadbackward.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/gcc/tree-ssa-threadbackward.c b/gcc/tree-ssa-threadbackward.c
index 542f422fd72..a28a20d6de1 100644
--- a/gcc/tree-ssa-threadbackward.c
+++ b/gcc/tree-ssa-threadbackward.c
@@ -827,6 +827,9 @@ pass_thread_jumps::execute (function *fun)
if (EDGE_COUNT (bb->succs) > 1)
backwards_threader.find_jump_threads_backwards (bb, true);
}
+ // FIXME: Put registry in thread_jumps and call thread_through_all_blocks
+ // from the destructor? Is it ok to call thread_through_all_blocks
+ // before loop_optimizer_finalize below?
bool changed = registry.thread_through_all_blocks (true);
loop_optimizer_finalize ();
@@ -889,6 +892,9 @@ pass_early_thread_jumps::execute (function *fun)
if (EDGE_COUNT (bb->succs) > 1)
backwards_threader.find_jump_threads_backwards (bb, false);
}
+ // FIXME: Put registry in thread_jumps and call thread_through_all_blocks
+ // from the destructor? Is it ok to call thread_through_all_blocks
+ // before loop_optimizer_finalize below?
registry.thread_through_all_blocks (true);
loop_optimizer_finalize ();
More information about the Gcc-cvs
mailing list