Dumping ttir and ttnn into json files #647
Draft
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
refactor, working for both ttir and ttnn
vkovinicTT
force-pushed
the
vkovinic/ttir_report
branch
from
74dd6c7
to
4a8325c
Compare
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.
This PR addresses issue #149 by adding functionality to
reportifyfor formatting and storing MLIR input (ttir) and MLIR output (ttnn) in a JSON file. With this update, running any module will save MLIR information within the pathtestify/ll-sw/%MODULE_NAME%/mlir_reportsasttir.mlirandttnn.mlir.