-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[REFACTOR][RELAY] Move invoke_tvm_op and shape_func to vm dialect #5958
Conversation
8713f6f
to
f1f02e2
Compare
Why change dialects? all of this machinery is probably needed for future work people want to do such as ahead of time compilation. cc @tqchen |
@jroesch aah, I am just separating them into memory and vm namespaces. For example, |
I think the separation makes sense if we agreed on the categorization. The common one should go to the memory dialect and the vm specific ones should goes into vm. @jroesch can you followup? |
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.
some minor comments
cbb6821
to
8d8f5ed
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
@jroesch Could you take a look again? |
…ache#5958) * [REFACTOR][RELAY] Move invoke_tvm_op and shape_func to vm dialect * address comments
…ache#5958) * [REFACTOR][RELAY] Move invoke_tvm_op and shape_func to vm dialect * address comments
This PR moves invoke_tvm_op and shape_func from memory dialect to vm dialect.
@icemelon9 @jroesch @wweic