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
In the above example, scf.if condition will only be satisfied when out of bound, yielding %cst of zero in such conditions.
Instead, we can potentially populate full static inner k loop with condition only in below situations:
For gemms that needs padding in the K dimension, the if/else condition check should be completely peeled out of the loop. There will be one additional deterministic extract_slice after K loop finish to perform another MFMA with padded zeros
For gemms that needs padding in the M or N dimension. In this case, majority of workgroups doesn't need the condition check except the tiles that happen to be in the boundary. We should think twice how to populate the kernel code to avoid the conditional check.
The text was updated successfully, but these errors were encountered:
When padding is enabled in #18858. We should peel away conditional check which turns out to be necessary only in boundary conditions.
In the above example, scf.if condition will only be satisfied when out of bound, yielding %cst of zero in such conditions.
Instead, we can potentially populate full static inner k loop with condition only in below situations:
The text was updated successfully, but these errors were encountered: