Repository navigation
Conversation
Member
|
Can you do a Sightglass run comparing compilation and benchmark performance with and without this commit, and posting the full output here? Thanks! |
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 #278.
try_allocating_regs_for_spilled_bundlestakes a register only when it has no conflict, but it passesmax_allowable_cost: None, so each attempt collects every conflicting bundle and then discards them. PassingSome(0)stops the scan at the first conflict with a nonzero spill weight.My ordinary test corpus (~20 programs of various shapes) compile with 0.14% fewer instructions.
For pathological programs,
Context::compilewith n values live across most of its blocks: