Displaying 3 results from an estimated 3 matches for "exitbb1".
2010 Oct 11
3
[LLVMdev] Specify dominator for BasicBlock to avoid "Instruction does not dominate all uses!"
...low correctly. Additionally, for each initial exit block I create an
associated block that will jump to the original successors of the exit
block.
In short:
B1 B2 B3 BB4
| | | |
\ | / |
ExitBB1 ExitBB2
| | | |
/ \ / \
EBB1.1 EBB1.2 EBB2.1 EBB2.2
becomes:
B1 B2 B3 BB4
| | | |
\ | /...
2010 Oct 11
0
[LLVMdev] Specify dominator for BasicBlock to avoid "Instruction does not dominate all uses!"
...h initial exit block I create an
> associated block that will jump to the original successors of the exit
> block.
> In short:
>
> B1 B2 B3 BB4
> | | | |
> \ | / |
> ExitBB1 ExitBB2
> | | | |
> / \ / \
> EBB1.1 EBB1.2 EBB2.1 EBB2.2
>
>
> becomes:
>
> B1 B2 B3 BB4
> | | |...
2010 Oct 12
1
[LLVMdev] Specify dominator for BasicBlock to avoid "Instruction does not dominate all uses!"
Hi, I tried adding the PHI nodes in BB_unique, and it works for the simple
case described here, but in case the nodes were declared in some
predecessors of ExitBB1 and used in ExitBB1_redirect and its successors, it
won't work, unless I create entries for all of them in BB_unique.
B1 (declares PHI_1) B3
| |
B2 |
|...