Repository navigation
Skip earlier vregs' blockparam inputs when placing moves - #281
Merged
Merged
Conversation
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
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.
Fixes #274.
apply_allocations_and_insert_movesresumes its walk ofblockparam_insfrom a cursor left by the previous vreg, butPrevBuffermoves the cursor only when a later range starts. A vreg with one range leaves it in place, and everyfollowing vreg rescans those entries. This skips the entries of earlier vregs, and corrects the sort order in the
comment above.
My ordinary test corpus (~20 programs of various shapes) compile time is unchanged.
For pathological programs, register allocation time with N loops in a row: