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
mlir printing and parsing fix #199
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Can you just add two tests for the printing and parsing of these things?
Also, is the printing of the FlatSymborRefAttr
implemented right now?
@math-fehr In which test file do you suggest to put the tests? |
Right, I'll make a PR to fix this issue, which will start executing this file. |
Hey @martin-luecke, is this PR still open? Is this sth we should tackle during the hackathon? |
Codecov ReportBase: 86.60% // Head: 88.80% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #199 +/- ##
==========================================
+ Coverage 86.60% 88.80% +2.20%
==========================================
Files 47 48 +1
Lines 6586 6603 +17
Branches 1107 1109 +2
==========================================
+ Hits 5704 5864 +160
+ Misses 650 504 -146
- Partials 232 235 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
7d67abe
to
d647295
Compare
- fix mlir parsing of symbol_ref - fix mlir printing of tensors with unknown sizes
d647295
to
e59632f
Compare
482b93c
to
4a9b98a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect!
Now printed as
tensor<?x128xf32>
instead oftensor<-1x128xf32>
.This is required for reparsing with mlir-opt