-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[MLIR][RemoveDeadValues] Mark arguments of a public function Live #160242
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
We should not do this when the analysis is not inter procedural, instead should just mark things live and return, otherwise we're gonna trigger race conditions here.
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.
That also points to a need for a test showing that when the pass is scheduled at the function level, we should make everything live and only optimize when scheduled at the module level.
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.
Hi, @joker-eph
I am new to the MLIR community. I make a tentative change to fix this problem. I'm open to alternatives. Next time, should I post on discourse and get a clear direction beforehand?
Are you suggesting RemoveDeadValues should support 2 modes?
How does RemoveDeadValues distinct two modes?
I think it's 1) by default. Actually, it caught me a surprise. I didn't realize that until I hit this bug.
In the downstream project, I inserted this code and has used it 3 months. It reconfigures 'Liveness dataflow' intra-procedural. It works to us, but it only eschews the bug, not solve it.
It just a boolean flag. now it is fixed in static. Should we make it configurable in runtime first?
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.
Function passes may run concurrently on different functions. Therefore, they should generally avoid looking at adjacent functions as that would cause race conditions. I'm not sure what will happen here as each pass may be computing its own instance of the liveness analysis scoped to the function it operates on so it may have no info at all about other functions. A straightforward fix to this is to make this a module pass so it cannot run on functions.
Uh oh!
There was an error while loading. Please reload this page.
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.
runOnFunction()
:If the pass is scheduled on a
func.func
, then this walk does not start on the module (despite the variable name) but on the function. And so it'll never visit the func.func itself and the processFuncOp won't be called.That said,
processCallOp
is gonna be called.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.
Here is an example of a fix where I detected whether we're working on a symbol table or not: 13ae9ea