chore(design): Moving to linear scan based register allocation - #13302
Open
aakoshh wants to merge 9 commits into
Open
chore(design): Moving to linear scan based register allocation#13302aakoshh wants to merge 9 commits into
aakoshh wants to merge 9 commits into
Conversation
5 tasks
4 tasks
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.
Problem Resolved
Related to #11638
Summary of Changes
Adds a
design/register_allocation.mddocument with a proposed phased transition from the current greedy register allocation algorithm to one based on linear scan, starting with a unified allocator interface.This is a live document that we can update based on discussions and during implementation (see the back-references in the comment history below).
User Documentation
Check one:
PR Checklist
cargo fmton default settings.