Change Details

Block A is a control dependency of block B, is A dominates B but B doesn't post dominate A. In detail: * Create the `CFGControlDependencyTree`, which in fact stores both a dominator and a post dominator tree * Add the new debug checker `debug.DumpControlDependencies` * Add both lit and unit tests. Now I'm not sure whether this is the optimal approach -- In fact I'm fairly certain that this isn't the most efficient way of calculating control dependencies, however, I'm not that concerned with performance just yet. This will be used to improve bug reports the static analyzer emits, and if this turns out to be useful, I might look enhancing this further.

~~Block A is a control dependency of block B, is A dominates B but B doesn't post dominate A.~~ In detail: * Create the `CFGControlDependencyTree`, which in fact stores both a dominator and a post dominator tree * Add the new debug checker `debug.DumpControlDependencies` * Add both lit and unit tests. Now I'm not sure whether this is the optimal approach -- In fact I'm fairly certain that this isn't the most efficient way of calculating control dependencies, however, I'm not that concerned with performance just yet. This will be used to improve bug reports the static analyzer emits, and if this turns out to be useful, I might look enhancing this further.

~~Block A is a control dependency of block B, is A dominates B but B doesn't post dominate A.~~ In detail: * Create the `CFGControlDependencyTree`, which in fact stores both a dominator and a post dominator tree * Add the new debug checker `debug.DumpControlDependencies` * Add both lit and unit tests. Now I'm not sure whether this is the optimal approach -- In fact I'm fairly certain that this isn't the most efficient way of calculating control dependencies, however, I'm not that concerned with performance just yet. This will be used to improve bug reports the static analyzer emits, and if this turns out to be useful, I might look enhancing this further.