tree d10452e4c25f813c0dce942189dd25273e8b3451
parent de797ddcb5d0a8b51c850e67ef2959f509953229
author Steven Perron <stevenperron@google.com> 1544209830 -0500
committer GitHub <noreply@github.com> 1544209830 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJcCsWmCRBK7hj4Ov3rIwAAdHIIADrIrVy4Pd0JAn8eesIyNIg8
 4Z32yDVyAiejZmRqZ4uaKvBAveUeENmWOY+ilFMd/8zzdwaPSZoXMvJe+2gdc4SS
 W7IT10L3RUpJ1YixD9OuXf6xvNpfRMj/LqXg09PxyRmUZzVg3yY87R6ikjeGo69x
 rpl10nVexFB/mQVAT/yj3GYiN30H7D9jrRvj5FLXFSkRya+tj23hkInDOTSaWxaT
 I2S3RmGx4lrNWLi0WvZIxrLBR0As0knwCw0BJJ4rEN9NtS59u8CgIuGrcPGVmyzU
 QokTUouw4jBQ+xC4G1rfYanumH95h8Vj0Zov1r3RF3ek5j2rBtpxsZai6GE7vaA=
 =pwaa
 -----END PGP SIGNATURE-----
 

Fix invalid OpPhi generated by merge-return. (#2172)

* Fix invalid OpPhi generated by merge-return.

When we create a new phi node for a value say %10, we have to replace
all of the uses of %10 that are no longer dominated by the def of %10
by the result id of the new phi.  However, if the use is in a phi node,
it is possible that the bb contains the use is not dominated by either.
In this case, needs to be handled differently.

* Split loop headers before add a new branch to them.

In merge return, Phi node in loop header that are also merges for loop
do not get updated correctly.  Those cases do not fit in with our
current analysis.  Doing this will simplify the code by reducing the
number of cases that have to be handled.