-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[AMDGPU][Scheduler] Scoring system for rematerialization candidates #153092
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
lucas-rami
wants to merge
16
commits into
llvm:main
Choose a base branch
from
lucas-rami:remat-score-system
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
4d68086
Scoring system for rematerializations
lucas-rami 534abd7
Format
lucas-rami 39f1f52
Address feedback + fix failing test
lucas-rami a681d9b
Remove REMAT_DEBUG and break ties in score
lucas-rami d4a0ccb
Fix failing tests and rollback mask change
lucas-rami 0f359d9
Address more feedback
lucas-rami 7ca1ba6
Rebase for new test + improve comment
lucas-rami bec1eba
Refactor scoring system + Remove always benef/latency calc
lucas-rami 03c229c
Fix tests
lucas-rami 0aafbb5
Improve code for frequency-based calculations
lucas-rami 256271e
Add empty region test
lucas-rami 458bc93
Correctly derive (sub)reg size and frequency fix
lucas-rami be6bf74
Walk over all regions to compute AchievedOcc
lucas-rami 6dd8bf2
Use std::max for freq calc.
lucas-rami 474f5d8
Simplify score calculation and improve debug
lucas-rami 0e1a6d8
Early exit on maxWavesPerEU and rebase
lucas-rami File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be
Remat < 0.Remat?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made the comparison in this direction because, all other things being equal, it will favor rematerializing registers with slightly longer live ranges in their defining regions.
Registers are collected in instruction order within each region so registers defined "early" in a region have lower addresses than those defined "late" in the same region. The former also have longer live-ranges in the region since they start earlier and extend to the live-outs. If the defining region is a region with excess RP this can lead to more optimal rematerializations overall in very specific cases (our remat unit tests actually hit that very specific case quite often due to their regular/artificial nature).