Add an info cast to prims.squeeze decomposition
#3844
Merged
+2
−1
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
zjgarvey
added a commit
to nod-ai/SHARK-TestSuite
that referenced
this pull request
Nov 1, 2024
With a fix in <llvm/torch-mlir#3844> for the model compilation issue, this test will pass with the change present here.
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.
The onnx ingest sometimes has poorly propagated shape information. E.g.:
... %9020 = torch.prims.squeeze %9010#1, %9019 : !torch.vtensor<[?,384,1],f32>, !torch.list<int> -> !torch.vtensor<[1,384],f32> return %9015, %9020 : !torch.vtensor<[1,384],f32>, !torch.vtensor<[1,384],f32> } }This occurred at the boundary of the onnx model
migraphx_bert__bert-large-uncased. Evidently, the output value tensor info had more information than could be propagated forward. ThePrimsSqueezelowering was returning a!torch.vtensor<[?,384],f32>which was causing a type mismatch with thefunc.return.