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 sure if we even need a class full of states, attributes, and methods to wrap CUtensorMap. I suspect we just need a lightweight class object + a free, factory function that takes a variety of configs and returns the object (i.e. no class constructor).
Unanswered question: Is CUtensorMap bound to a CUDA context?
The text was updated successfully, but these errors were encountered:
Asked internally and the answer is yes. It means the TensorMap object would need to offer a reverse lookup to device/context, as done in other objects.
I am not sure if we even need a class full of states, attributes, and methods to wrap
CUtensorMap
. I suspect we just need a lightweight class object + a free, factory function that takes a variety of configs and returns the object (i.e. no class constructor).Unanswered question: Is
CUtensorMap
bound to a CUDA context?The text was updated successfully, but these errors were encountered: