-
Notifications
You must be signed in to change notification settings - Fork 80
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: (linalg) fix linalg.matmul
to correctly store integer arg types
#3903
base: main
Are you sure you want to change the base?
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.
This is great, could you please add a test?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3903 +/- ##
==========================================
+ Coverage 91.26% 91.29% +0.03%
==========================================
Files 468 466 -2
Lines 57998 58012 +14
Branches 5566 5566
==========================================
+ Hits 52929 52962 +33
+ Misses 3646 3622 -24
- Partials 1423 1428 +5 ☔ View full report in Codecov by Sentry. |
// CHECK-GENERIC-NEXT: %45 = "arith.muli"(%42, %44) <{overflowFlags = #arith.overflow<none>}> : (i32, i32) -> i32 | ||
// CHECK-GENERIC-NEXT: %46 = "arith.addi"(%40, %45) <{overflowFlags = #arith.overflow<none>}> : (i32, i32) -> i32 | ||
// CHECK-GENERIC-NEXT: "linalg.yield"(%46) : (i32) -> () | ||
// CHECK-GENERIC-NEXT: ^11(%41 : i8, %42 : i8, %43 : i32, %44 : i32, %45 : i32): |
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.
@superlopuh @compor Just curious, why do we use integer values here instead of capturing patterns like %{{.*}}
?
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.
as far as I'm concerned, that's a bug, maybe these should be fixed in this PR
@superlopuh @compor