-
Notifications
You must be signed in to change notification settings - Fork 95
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
Prefill fix for multiple output cases #3605
Merged
Merged
Conversation
This file contains 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
I included the MLIR bump from #3586 since thats where we first found this bug. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3605 +/- ##
=========================================
Coverage 92.16% 92.17%
=========================================
Files 512 513 +1
Lines 21412 21536 +124
=========================================
+ Hits 19735 19851 +116
- Misses 1677 1685 +8 ☔ View full report in Codecov by Sentry. |
pfultz2
approved these changes
Nov 11, 2024
This build is not recommended to merge 🔴 |
🔴bert_large_uncased_fp16: FAILED: MIGraphX is not within tolerance - check verbose output |
CharlieL7
approved these changes
Nov 11, 2024
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.
Background:
If we request a mlir kernel with multiple outputs, the output buffer will be allocated as a tuple. Example IR before compile_ops pass:
Bug:
Our code is not able to prefill a buffer in the multi output case
Fix:
MLIR doesnt accept tuples and so we flatten them when giving inputs to mlir code objects. Same type of flattening needs to happen when determining which buffers in the allocated tuple need to be prefilled.
Assumptions:
If either of those assumptions become untrue in the future, we will need better logic to hand this.