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
I am looking into DLPack as we likely need to fix it for ROCm (it supports the kDLROCM option). One thing I noticed is that we basically reimplemented everything from the DLPack header dlpack.h in cupy/core/dlpack.pyx. I suppose like Jitify it's also a single header thing, so we might as well make it a submodule?
This will also prepare us for the Python Array API involvement, for which DLPack is being considered as the data exchange format (data-apis/consortium-feedback#1; see also the Array API Standard draft), but it currently lacks
I am looking into DLPack as we likely need to fix it for ROCm (it supports the
kDLROCM
option). One thing I noticed is that we basically reimplemented everything from the DLPack headerdlpack.h
incupy/core/dlpack.pyx
. I suppose like Jitify it's also a single header thing, so we might as well make it a submodule?This will also prepare us for the Python Array API involvement, for which DLPack is being considered as the data exchange format (data-apis/consortium-feedback#1; see also the Array API Standard draft), but it currently lacks
so it will likely be revised in the near future. If this is acceptable then please assign it to me.
The text was updated successfully, but these errors were encountered: