You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Incorrect Padding Dimension Check in MLIR Validation
Description:
Forge-FE provides padding values in the order [pT, pL, pB, pR]. However, the MLIR implementation currently checks the dimensions incorrectly. Instead of validating that the top and bottom paddings are equal (p[0] == p[2]) and the left and right paddings are equal (p[1] == p[3]), the code mistakenly compares p[0] == p[1] and p[2] == p[3]. This results in false validation errors when the frontend sends correctly structured padding.
The top and bottom paddings should be equal: p[0] == p[2]
The left and right paddings should be equal: p[1] == p[3]
Actual Behavior:
The current logic compares:
p[0] == p[1]
p[2] == p[3]
which does not correctly represent the intended padding semantics.
Suggested Fix:
Modify the validation logic in the MLIR component to check:
p[0] == p[2] (Top equals Bottom)
p[1] == p[3] (Left equals Right)
Additional Context:
This issue affects the integration between the frontend and MLIR, causing unexpected errors even when the padding is correctly provided.
The text was updated successfully, but these errors were encountered:
### Ticket
#2389
### Problem description
Forge-FE provides padding values in the order [pT, pL, pB, pR]. However, the MLIR implementation currently checks the dimensions incorrectly. Instead of validating that the top and bottom paddings are equal (p[0] == p[2]) and the left and right paddings are equal (p[1] == p[3]), the code mistakenly compares p[0] == p[1] and p[2] == p[3]. This results in false validation errors when the frontend sends correctly structured padding.
### What's changed
Fixed an error in comparison. Added both positive and negative test (for padding) for TTIR->TTNN conversion of `conv_transpose2d` op.
### Checklist
- [x] New/Existing tests provide coverage for changes
Incorrect Padding Dimension Check in MLIR Validation
Description:
Forge-FE provides padding values in the order
[pT, pL, pB, pR]
. However, the MLIR implementation currently checks the dimensions incorrectly. Instead of validating that the top and bottom paddings are equal (p[0] == p[2]
) and the left and right paddings are equal (p[1] == p[3]
), the code mistakenly comparesp[0] == p[1]
andp[2] == p[3]
. This results in false validation errors when the frontend sends correctly structured padding.TTIR:
Expected Behavior:
p[0] == p[2]
p[1] == p[3]
Actual Behavior:
The current logic compares:
p[0] == p[1]
p[2] == p[3]
which does not correctly represent the intended padding semantics.
Suggested Fix:
Modify the validation logic in the MLIR component to check:
p[0] == p[2]
(Top equals Bottom)p[1] == p[3]
(Left equals Right)Additional Context:
This issue affects the integration between the frontend and MLIR, causing unexpected errors even when the padding is correctly provided.
The text was updated successfully, but these errors were encountered: