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 not able to dig deep into this right now, but there are a couple of additional potential hurdles for the CUDA target:
The CUDA Ufunc mechanism doesn't yet support dynamic Ufuncs, which seem to be a part of the implementation of the PR for the CPU target.
The __array_ufunc__ mechanism seems CPU-centric - will we need to define a new __cuda_array_ufunc__ mechanism for this to be practical? c.f. __cuda_array_interface__ vs. __array_interface__.
The text was updated successfully, but these errors were encountered:
Details / notes:
From Allow libraries that implement array_ufunc to override CUDAUFuncDispatcher on the Numba Discourse.
There was a PR implementing this for the CPU target: numba/numba#8995
A related issue on the Awkward issue tracker: scikit-hep/awkward#3179
This is to support using Coffea on CUDA.
cc @ianna @lgray
Initial thoughts:
I am not able to dig deep into this right now, but there are a couple of additional potential hurdles for the CUDA target:
__array_ufunc__
mechanism seems CPU-centric - will we need to define a new__cuda_array_ufunc__
mechanism for this to be practical? c.f.__cuda_array_interface__
vs.__array_interface__
.The text was updated successfully, but these errors were encountered: