Previously the tied operand and result operand had to match ShapedType exactly. I am relaxing it to allow dynamic shapes on one side and static shapes on the other, as some Linalg Transformations (like Padding) creates dynamic shapes. The rationale is that a dynamic dimension can be potentially unified with any dimension value.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm not convinced that this is the fix... The result type and operand type should match based on my understanding about DPS interface. (I could be wrong though)
Comment Actions
The latest padding transformation https://github.com/llvm/llvm-project/commit/6d2501bf00f662ef05731aa7c59351467aac2a70 creates dynamic types. So @nicolasvasilache can chime in and fix it correctly?
Comment Actions
shapes need to match, I am unclear why you need this and why there is no clear test that exercises such fundamental changes