-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[MetaSchedule][M4a] Rewrite-Cooperative-Fetch #10081
[MetaSchedule][M4a] Rewrite-Cooperative-Fetch #10081
Conversation
Hey please rebase to the latest main |
d90b791
to
4c3ba47
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Only have some nits. Thank you Siyuan!
4c3ba47
to
ce52b56
Compare
Co-authored-by: Junru Shao <[email protected]> Co-authored-by: Xiyou Zhou <[email protected]> Co-authored-by: Bohan Hou <[email protected]> Co-authored-by: Ruihang Lai <[email protected]> Co-authored-by: Hongyi Jin <[email protected]> Co-authored-by: Wuwei Lin <[email protected]>
ce52b56
to
70c014e
Compare
Co-authored-by: Junru Shao <[email protected]> Co-authored-by: Xiyou Zhou <[email protected]> Co-authored-by: Bohan Hou <[email protected]> Co-authored-by: Ruihang Lai <[email protected]> Co-authored-by: Hongyi Jin <[email protected]> Co-authored-by: Wuwei Lin <[email protected]> Co-authored-by: Junru Shao <[email protected]> Co-authored-by: Xiyou Zhou <[email protected]> Co-authored-by: Bohan Hou <[email protected]> Co-authored-by: Ruihang Lai <[email protected]> Co-authored-by: Hongyi Jin <[email protected]> Co-authored-by: Wuwei Lin <[email protected]>
tir::ParseThreadBinding(sch, inst, "threadIdx.y")) { | ||
thread_extent_y = new_thread_extent.value()->value; | ||
} else if (Optional<tir::BlockRV> block_rv = tir::ParseAnnotate(sch, inst, &vector_lane)) { | ||
ICHECK_NE(thread_extent_x, -1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this check necessary here? I am hitting this check with a simple matmul_fp16
example with rules and postprocs like in test_meta_schedule_tune_tir
and I wonder if more details about this check can be elaborated here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it means threadIdx.x
isn't bound in previous instructions, which isn't supposed to happen (and that's why it's an ICHECK instead of CHECK). Could you check the trace->insts
and see why threadIdx.x
doesn't exist previously
It is one of the PostProc for mate-schedule. Please see the tracking issue #8473
Co-authored-by: Junru Shao [email protected]
Co-authored-by: Xiyou Zhou [email protected]
Co-authored-by: Bohan Hou [email protected]
Co-authored-by: Ruihang Lai [email protected]
Co-authored-by: Hongyi Jin [email protected]
Co-authored-by: Wuwei Lin [email protected]
cc @junrushao1994 @comaniac