tree 346f7b15a62ff1b0821ebde99a692f72bd3155ae
parent c9190a54da56e425d09e122368b18bcfe00dabf6
author Steven Perron <stevenperron@google.com> 1563991014 -0400
committer GitHub <noreply@github.com> 1563991014 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJdOJvmCRBK7hj4Ov3rIwAAdHIIAK39G6thNArSZtx8IWgt/A/P
 vuk0Ua1Mtsqh939FR4IKmu3Fkj8WKAXY4LT3yeinTityQVQxmEHAXLzewHXf0+rW
 t53aYzrmnQvGfsYnnhMUtpLKZAOAPZ69aoDXopvWwe7oJGyYJ66VwdwjYp3HzbE+
 3Ch7JW42SfANe8i2sg9jDbzkbXWGzOJzIDw05l/P+XBrV0e0k5b0y0RyHDoj8/KL
 bRU/TX9G//j5qYIo05Dx9tdlt9NGNxmZ44ExkSdc8A3sXXvTjoKXnswX2ccqunXV
 df62kSLKAdsx2GsBrQO+7H7iHe6GkQtzRodGh3gQM+tDYgU+cJXYnn2hcx2xYDw=
 =NrXg
 -----END PGP SIGNATURE-----
 

Record correct dominators in merge return (#2760)

In merge return, we need to know the original dominator for a block in order to
traverse code from the original dominator to the new dominator and add
appropriate Phi nodes.  The current code gets this wrong because the dominator
tree is build as needed.  The first time we get the immediate dominator for a
function we just built the dominator tree and it takes into account that a
block has been split.  The second time it does not.

This inconsistency needs to be fixed.  We do that by recording the original
dominator for all blocks at the start of the pass.

If we were to record just the basic block, that could change if the block is
split.  We want to traverse the code in the body of the original dominator,
whatever block it ends up in.  To make this easy to track, we not save the
terminator instruction to represent the original dominator.

Fixes #2745