-
Notifications
You must be signed in to change notification settings - Fork 522
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
[RFC] aten.to.device #1075
Comments
Once the program is converted to value semantics it becomes an identity operation. |
Okay, I'll implement it as a decomposition to |
qedawkins
pushed a commit
to nod-ai/torch-mlir
that referenced
this issue
Oct 3, 2022
* Add ScatterElementsOp and RoiAlignOp inferShapes, with dynamic shape support and separate verifier. Signed-off-by: PengQi220 <[email protected]> Co-authored-by: Alexandre Eichenberger <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running into calls to
aten.to.device
in a model and I was wondering how we want to handle it. It looks like we should just be able to replace it with a conversion but I wanted to double check if we wanted to handle the logic of moving tensors between devices.The text was updated successfully, but these errors were encountered: