1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
|
/* Generic dominator tree walker
Copyright (C) 2003-2015 Free Software Foundation, Inc.
Contributed by Diego Novillo <dnovillo@redhat.com>
This file is part of GCC.
GCC is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3, or (at your option)
any later version.
GCC is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
#include "config.h"
#include "system.h"
#include "coretypes.h"
#include "tm.h"
#include "predict.h"
#include "vec.h"
#include "hashtab.h"
#include "hash-set.h"
#include "machmode.h"
#include "hard-reg-set.h"
#include "input.h"
#include "function.h"
#include "dominance.h"
#include "cfg.h"
#include "cfganal.h"
#include "basic-block.h"
#include "domwalk.h"
#include "sbitmap.h"
/* This file implements a generic walker for dominator trees.
To understand the dominator walker one must first have a grasp of dominators,
immediate dominators and the dominator tree.
Dominators
A block B1 is said to dominate B2 if every path from the entry to B2 must
pass through B1. Given the dominance relationship, we can proceed to
compute immediate dominators. Note it is not important whether or not
our definition allows a block to dominate itself.
Immediate Dominators:
Every block in the CFG has no more than one immediate dominator. The
immediate dominator of block BB must dominate BB and must not dominate
any other dominator of BB and must not be BB itself.
Dominator tree:
If we then construct a tree where each node is a basic block and there
is an edge from each block's immediate dominator to the block itself, then
we have a dominator tree.
[ Note this walker can also walk the post-dominator tree, which is
defined in a similar manner. i.e., block B1 is said to post-dominate
block B2 if all paths from B2 to the exit block must pass through
B1. ]
For example, given the CFG
1
|
2
/ \
3 4
/ \
+---------->5 6
| / \ /
| +--->8 7
| | / |
| +--9 11
| / |
+--- 10 ---> 12
We have a dominator tree which looks like
1
|
2
/ \
/ \
3 4
/ / \ \
| | | |
5 6 7 12
| |
8 11
|
9
|
10
The dominator tree is the basis for a number of analysis, transformation
and optimization algorithms that operate on a semi-global basis.
The dominator walker is a generic routine which visits blocks in the CFG
via a depth first search of the dominator tree. In the example above
the dominator walker might visit blocks in the following order
1, 2, 3, 4, 5, 8, 9, 10, 6, 7, 11, 12.
The dominator walker has a number of callbacks to perform actions
during the walk of the dominator tree. There are two callbacks
which walk statements, one before visiting the dominator children,
one after visiting the dominator children. There is a callback
before and after each statement walk callback. In addition, the
dominator walker manages allocation/deallocation of data structures
which are local to each block visited.
The dominator walker is meant to provide a generic means to build a pass
which can analyze or transform/optimize a function based on walking
the dominator tree. One simply fills in the dominator walker data
structure with the appropriate callbacks and calls the walker.
We currently use the dominator walker to prune the set of variables
which might need PHI nodes (which can greatly improve compile-time
performance in some cases).
We also use the dominator walker to rewrite the function into SSA form
which reduces code duplication since the rewriting phase is inherently
a walk of the dominator tree.
And (of course), we use the dominator walker to drive our dominator
optimizer, which is a semi-global optimizer.
TODO:
Walking statements is based on the block statement iterator abstraction,
which is currently an abstraction over walking tree statements. Thus
the dominator walker is currently only useful for trees. */
static int *bb_postorder;
static int
cmp_bb_postorder (const void *a, const void *b)
{
basic_block bb1 = *(basic_block *)const_cast<void *>(a);
basic_block bb2 = *(basic_block *)const_cast<void *>(b);
if (bb1->index == bb2->index)
return 0;
/* Place higher completion number first (pop off lower number first). */
if (bb_postorder[bb1->index] > bb_postorder[bb2->index])
return -1;
return 1;
}
/* Recursively walk the dominator tree.
BB is the basic block we are currently visiting. */
void
dom_walker::walk (basic_block bb)
{
basic_block dest;
basic_block *worklist = XNEWVEC (basic_block,
n_basic_blocks_for_fn (cfun) * 2);
int sp = 0;
int *postorder, postorder_num;
if (m_dom_direction == CDI_DOMINATORS)
{
postorder = XNEWVEC (int, n_basic_blocks_for_fn (cfun));
postorder_num = inverted_post_order_compute (postorder);
bb_postorder = XNEWVEC (int, last_basic_block_for_fn (cfun));
for (int i = 0; i < postorder_num; ++i)
bb_postorder[postorder[i]] = i;
free (postorder);
}
while (true)
{
/* Don't worry about unreachable blocks. */
if (EDGE_COUNT (bb->preds) > 0
|| bb == ENTRY_BLOCK_PTR_FOR_FN (cfun)
|| bb == EXIT_BLOCK_PTR_FOR_FN (cfun))
{
/* Callback for subclasses to do custom things before we have walked
the dominator children, but before we walk statements. */
before_dom_children (bb);
/* Mark the current BB to be popped out of the recursion stack
once children are processed. */
worklist[sp++] = bb;
worklist[sp++] = NULL;
int saved_sp = sp;
for (dest = first_dom_son (m_dom_direction, bb);
dest; dest = next_dom_son (m_dom_direction, dest))
worklist[sp++] = dest;
if (m_dom_direction == CDI_DOMINATORS)
switch (sp - saved_sp)
{
case 0:
case 1:
break;
default:
qsort (&worklist[saved_sp], sp - saved_sp,
sizeof (basic_block), cmp_bb_postorder);
}
}
/* NULL is used to mark pop operations in the recursion stack. */
while (sp > 0 && !worklist[sp - 1])
{
--sp;
bb = worklist[--sp];
/* Callback allowing subclasses to do custom things after we have
walked dominator children, but before we walk statements. */
after_dom_children (bb);
}
if (sp)
bb = worklist[--sp];
else
break;
}
if (m_dom_direction == CDI_DOMINATORS)
{
free (bb_postorder);
bb_postorder = NULL;
}
free (worklist);
}
|
