-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[mlir][scf] Fix scf.forall to scf.parallel pass walker #95385
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
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
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.
Is this a failure? Why remove the
signalPassFailure()
?There is also likely a missing error message before
signalPassFailure()
here (we shouldn't fail silently).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.
The result is not a real failure as it only occurs on match failure.
The main motivation for the change is that simply calling
signalPassFailure()
produces no output when the pass is called (at least from CLI). I'd expect the IR to remain unchanged in such case.I think I should've captures the walk result and added some error on interruption. But there is no reason to interrupt on this error.
Perhaps a greedy rewriter could be better here instead of walking the graph manually.
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.
The
scf::forallToParallelLoop
function internally callsnotifyMatchFailure
, so some diagnostic should occur. That may not mean much if the pass terminates successfully though.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.
notifyMatchFailure
is a debug function. This is a question of semantics for the pass though, and unfortunately this pass does not even have a description!Can we start here and document the pass behavior before changing it?
(is the pass promising to turn all ForAll to scf.parallel? Or it is opportunistically doing it? Under which conditions? etc)
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.
The lack of description is my fault. My original intention was to error out when
scf.forall
cannot be lowered. I don't think it makes sense to run this transform before bufferization, and after bufferization allscf.forall
operations should produce no results.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.
Good points all together. My change was too eager too.
@sabauma My view on the pass is that indicating full failure (through
signalPassFailure
) is a bit heavy handed in this case (and viewed it as "error") but if that is the intention, it is equally valid approach.I'll leave the pass as is. Perhaps the description could be explicit about the intended behavior.