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
We allow a separate device field to be specified even when initializing Tripy Tensor with a DLPack object. Since Tripy Tensor must not perform any implicit copies, we assert if the device does not conform to the DLPack object data pointer device location. Once #72 is merged, we will not be performing such a check in the front-end.
There are three options:
Do not allow specifying the device field in the Tensor initializer if initializing with a DLPack object.
Add the check back to the Tripy front-end. This would need access to cupy as far as I can tell.
Add the check to MLIR-TensorRT. This should be trivial to add.
The text was updated successfully, but these errors were encountered:
We allow a separate device field to be specified even when initializing Tripy Tensor with a DLPack object. Since Tripy Tensor must not perform any implicit copies, we assert if the device does not conform to the DLPack object data pointer device location. Once #72 is merged, we will not be performing such a check in the front-end.
There are three options:
The text was updated successfully, but these errors were encountered: