Update the return type of the get_op_constraints API to match tt-metal #1923
+1
−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
arminaleTT
added
the
TTNN Constraints&L1
arminaleTT
requested review from
odjuricicTT,
tt-mpantic and
sdjordjevicTT
as code owners
mbezuljTT
approved these changes
Jan 22, 2025
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.
Issue: #1922
In tenstorrent/tt-metal#16921 I am proposing to change the name of a struct that is defined in metal but also used and explicitly named in this repo. This PR updates the name to match the proposed name in metal
Note: both PRs need to be sequenced properly with the metal uplift to ensure the mlir build is unaffected