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
The wrapped pointer_t class is nice, but - we shouldn't have to create a wrapped object only to run the method which obtains the device or the context for a pointer. There should be freestanding functions which do that.
The text was updated successfully, but these errors were encountered:
* Can now get the device for a pointer in CUDA before 9.2 - by getting the context, then getting the device for the context
* Added `memory::device_of()` and `memory::context_of()`
* Added `memory::detail_` functions for returning the context handle or device id of a pointer, without having to remember the pointer attributes mechanism
* Can now get the device for a pointer in CUDA before 9.2 - by getting the context, then getting the device for the context
* Added `memory::device_of()` and `memory::context_of()`
* Added `memory::detail_` functions for returning the context handle or device id of a pointer, without having to remember the pointer attributes mechanism
* Can now get the device for a pointer in CUDA before 9.2 - by getting the context, then getting the device for the context
* Added `memory::device_of()` and `memory::context_of()`
* Added `memory::detail_` functions for returning the context handle or device id of a pointer, without having to remember the pointer attributes mechanism
The wrapped pointer_t class is nice, but - we shouldn't have to create a wrapped object only to run the method which obtains the device or the context for a pointer. There should be freestanding functions which do that.
The text was updated successfully, but these errors were encountered: