Drop insertion: resolve the release of a loop-carried pair of phis - #4
Merged
Merged
Conversation
A phi's release is decided with an undecided candidate phi among its incomings left open, then every decision is checked against all incomings and withdrawn until they agree, so a header phi and a merge phi naming each other both own and release what they replace. git-bug: 3d85c96d580f3ab6588ea1646cb5431a01da7bba366e41964e808a6e2732f151
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A phi's release is decided with an undecided candidate phi among its incomings left open, then every decision is checked against all incomings and withdrawn until they agree, so a header phi and a merge phi naming each other both own and release what they replace.
git-bug: 3d85c96d580f3ab6588ea1646cb5431a01da7bba366e41964e808a6e2732f151