llvm.org GIT mirror llvm / d5fcbff
A little wordsmithing of dominator verification comments. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@306916 91177308-0d34-0410-b5e6-96231b3b80d8 Daniel Berlin 3 years ago
1 changed file(s) with 6 addition(s) and 6 deletion(s). Raw diff Collapse all Expand all
334334
335335 // The easiest way to think of the parent property is that it's a requirement
336336 // of being a dominator. Let's just take immediate dominators. For PARENT to
337 // be an immediate dominator of CHILD, all paths must go through PARAENT
338 // before they hit CHILD. This implies that if you were to cut PARENT out of
339 // the CFG, there should be no paths to CHILD that are reachable. If there
340 // were, then you now have a path from PARENT to CHILD that goes around PARENT
341 // and still reaches the target node, which by definition, means PARENT can't
342 // be a dominator (let alone an immediate one).
337 // be an immediate dominator of CHILD, all paths in the CFG must go through
338 // PARENT before they hit CHILD. This implies that if you were to cut PARENT
339 // out of the CFG, there should be no paths to CHILD that are reachable. If
340 // there are, then you now have a path from PARENT to CHILD that goes around
341 // PARENT and still reaches CHILD, which by definition, means PARENT can't be
342 // a dominator of CHILD (let alone an immediate one).
343343
344344 // The sibling property is similar. It says that for each pair of sibling
345345 // nodes in the dominator tree (LEFT and RIGHT) , they must not dominate each