-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename unroll_n_to_subgroups
to subgroups_n
#19102
Conversation
|
Interesting. I parsed "distribute to subgroups" as the action of distributing to the preestablished number of subgroups, while here, the effect is to set/increase the number of subgroups. WDYT? |
Hmmm I parsed the field as "this dimension will be distributed to subgroups" as an analog to "this dimension will be unrolled to more instructions" |
Yeah but the nuance is that this field is what causes this dimension to be created in the first place. |
I see, so really we have two distinct names occupying the same field of the attribute. Before I would think that the name of the field in the |
Before
MaterializeEncoding is a type-conversion pass, and that is necessary anyway to have well-formed multi_mma ops.
From |
Just discussed online with @qedawkins and we agreed on |
58beb25
to
a89bc41
Compare
f58d8cb
to
82cbb2f
Compare
7c3f370
to
d0eb097
Compare
82cbb2f
to
b69eb02
Compare
unroll_n_to_subgroups
to subgroups_n
Do you also need to update the PR description? |
d0eb097
to
47232f2
Compare
b69eb02
to
7ffd79a
Compare
47232f2
to
3081305
Compare
7ffd79a
to
1f71536
Compare
In `getIntrinsicSwizzle`, we had a slightly roundabout way of constructing the swizzle from the `SingleSubgroupLayout`. We started from the `thread` dims, which we used unconditionally even if they had the value 1, leading to unit dims; and then we inserted the `element` dims *on the inside*, which required custom manipulation of the `swizzle` field. Now we just start from the `element` dims and work our way outwards from there, which means we can reuse the same helper that used to be named `unroll` and that we rename here to `expand` in preparation for #19102, and which we also move to be a `static` helper since it's no longer used outside of this file. --------- Signed-off-by: Benoit Jacob <[email protected]>
Signed-off-by: Benoit Jacob <[email protected]>
1f71536
to
b318881
Compare
…19105) In `getIntrinsicSwizzle`, we had a slightly roundabout way of constructing the swizzle from the `SingleSubgroupLayout`. We started from the `thread` dims, which we used unconditionally even if they had the value 1, leading to unit dims; and then we inserted the `element` dims *on the inside*, which required custom manipulation of the `swizzle` field. Now we just start from the `element` dims and work our way outwards from there, which means we can reuse the same helper that used to be named `unroll` and that we rename here to `expand` in preparation for iree-org#19102, and which we also move to be a `static` helper since it's no longer used outside of this file. --------- Signed-off-by: Benoit Jacob <[email protected]>
"Unroll" usually means "generate more instructions", so the terminology being changed here, `unroll_n_to_subgroups`, created confusion. Signed-off-by: Benoit Jacob <[email protected]>
…19105) In `getIntrinsicSwizzle`, we had a slightly roundabout way of constructing the swizzle from the `SingleSubgroupLayout`. We started from the `thread` dims, which we used unconditionally even if they had the value 1, leading to unit dims; and then we inserted the `element` dims *on the inside*, which required custom manipulation of the `swizzle` field. Now we just start from the `element` dims and work our way outwards from there, which means we can reuse the same helper that used to be named `unroll` and that we rename here to `expand` in preparation for iree-org#19102, and which we also move to be a `static` helper since it's no longer used outside of this file. --------- Signed-off-by: Benoit Jacob <[email protected]> Signed-off-by: Giacomo Serafini <[email protected]>
"Unroll" usually means "generate more instructions", so the terminology being changed here, `unroll_n_to_subgroups`, created confusion. Signed-off-by: Benoit Jacob <[email protected]> Signed-off-by: Giacomo Serafini <[email protected]>
"Unroll" usually means "generate more instructions", so the terminology being changed here,
unroll_n_to_subgroups
, created confusion.