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
This leads to indexing failure with T0 and T2 since the left of their ca pos are loop mapped to broadcasted Iterdomains so we'd need to use permissive mapping instead of exact mapping to bind the index for, say, iS15{128}, and currently we are only doing this for leaf domains / loop ids:
Thoroughly fixing this one would take a bit of formalization, potentially with additional pass on concrete indices or a different traversal order. Would appreciate any suggestions.
Meanwhile I guess we could detect this usage and assert on them.
Versions
N/A
The text was updated successfully, but these errors were encountered:
shmsong
changed the title
[Indexing failure] Need to find right binding on the right of CA axis.
[Indexing failure] Need to find right binding on the inner side of CA axis.
Jul 28, 2022
shmsong
changed the title
[Indexing failure] Need to find right binding on the inner side of CA axis.
[Indexing failure] Need to find permissive index binding on the inner side of CA axis.
Jul 28, 2022
馃悰 Describe the bug
We have an unsupported case currently with inlined broadcasting.
Minimum repro:
Error message:
Fusion debug print:
This leads to indexing failure with T0 and T2 since the left of their ca pos are loop mapped to broadcasted Iterdomains so we'd need to use permissive mapping instead of exact mapping to bind the index for, say,
iS15{128}
, and currently we are only doing this for leaf domains / loop ids:https://github.com/csarofeen/pytorch/blob/devel/torch/csrc/jit/codegen/cuda/lower_index_compute.cpp#L714-L715
Thoroughly fixing this one would take a bit of formalization, potentially with additional pass on concrete indices or a different traversal order. Would appreciate any suggestions.
Meanwhile I guess we could detect this usage and assert on them.
Versions
N/A
The text was updated successfully, but these errors were encountered: