On Tuesday, 21 October 2014 at 08:31:03 UTC, ponce wrote:
On Thursday, 16 October 2014 at 21:18:15 UTC, ponce wrote:
Dear D users,
I'd like to announce DerelictCUDA, dynamic bindings to the
CUDA library.
https://github.com/derelictorg/derelictcuda
For now, only the CUDA Driver API is exposed, providing most
of the warp control.
For a visual explanation of the different APIs in CUDA, see
http://stackoverflow.com/questions/242894/cuda-driver-api-vs-cuda-runtime
More APIs could be implemented if the interest happens to be
non-null.
CUDA Runtime API added.
This is great! I know that C++ uses <<< and >>> to enclose kernel
calls and thus create the link between CPU and GPU code when NVCC
rips things apart. How is this done in your bindings?
