Skip to content
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

dialects: (tosa) turn attributes into properties #3188

Merged
merged 3 commits into from
Sep 19, 2024
Merged

Conversation

jorendumoulin
Copy link
Collaborator

The attributes are actually properties in tosa.
I got fooled by the ParsePropInAttrDict ☹️

better ordering

formatting
@jorendumoulin jorendumoulin marked this pull request as draft September 18, 2024 05:51
Copy link

codecov bot commented Sep 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.02%. Comparing base (c9c6df3) to head (0d7eae3).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3188   +/-   ##
=======================================
  Coverage   90.02%   90.02%           
=======================================
  Files         431      431           
  Lines       54258    54259    +1     
  Branches     8404     8404           
=======================================
+ Hits        48845    48848    +3     
+ Misses       4055     4054    -1     
+ Partials     1358     1357    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jorendumoulin jorendumoulin marked this pull request as ready for review September 18, 2024 05:58
Copy link
Member

@superlopuh superlopuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes me think that it's probably worth adding a roundtrip test with MLIR to make sure we're consistent

@superlopuh superlopuh added the dialects Changes on the dialects label Sep 18, 2024
@jorendumoulin
Copy link
Collaborator Author

That's the funny thing, there are mlir interop tests, however, as most interop tests, I only used it with custom printing. The check thus didn't notice a difference between attributes or properties that are custom printed as attributes.

Does it make sense to change

// RUN: xdsl-opt %s | xdsl-opt | mlir-opt | filecheck %s

Into

// RUN: xdsl-opt %s | xdsl-opt --print-op-generic | mlir-opt --mlir-print-op-generic | xdsl-opt | mlir-opt | filecheck %s

?

@superlopuh
Copy link
Member

Oh interesting. Yeah maybe we should have both indeed, I doubt it will have a significant overhead in time

@jorendumoulin jorendumoulin merged commit c0713ea into main Sep 19, 2024
13 checks passed
@jorendumoulin jorendumoulin deleted the joren/fix-tosa branch September 19, 2024 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dialects Changes on the dialects
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants