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
The current syntax for workgroup count ops has a trailing operand list,
which is problematic when the following op has results, e.g.:
```mlir
%x, %y, %z = iree_tensor_ext.dispatch.workgroup_count_from_slice
%foo = arith.constant 1 : index
```
gets parsed as:
```mlir
%x, %y, %z = iree_tensor_ext.dispatch.workgroup_count_from_slice %foo
= arith.constant 1 : index
```
and errors out.
So far this hasn't been an issue, as the workgroup count ops are
typically followed by a `return`, which has no results, but with the
introduction of `workgroup_count_split_reduction_modifier` we've begun
hitting this case more often. This updates the syntax to have additional
literals which remove the ambiguity.
Syntax change:
Before:
```mlir
iree_tensor_ext.dispatch.workgroup_count_from_slice
iree_tensor_ext.dispatch.workgroup_count_split_reduction_modifier(%x, %y, %z),
iree_tensor_ext.dispatch.workgroup_count_from_dag_root
```
After:
```mlir
iree_tensor_ext.dispatch.workgroup_count_from_slice()
iree_tensor_ext.dispatch.workgroup_count_split_reduction_modifier workgroups(%x, %y, %z) workload()
iree_tensor_ext.dispatch.workgroup_count_from_dag_root()
```
Signed-off-by: keshavvinayak01 <[email protected]>
0 commit comments