#8364: Disable implicit fallback for ttnn.pad #8742
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
ayerofieiev-tt
requested review from
eyonland,
arakhmati,
cfjchu and
xanderchin
as code owners
ayerofieiev-tt
force-pushed
the
ay/issue-8364-pad
branch
from
4fe94d3
to
5bd0bac
Compare
arakhmati
approved these changes
May 22, 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.
What's happening
This is a part of the #8364 effort
Model developers now have to explicitly use torch fallback when
ttnn.paddoes not work on a given input.Automatic/implicit fallback is disabled in this PR.
Use
ttnn.get_fallback_function(ttnn.pad)Update
CI Results