cuda-api-wrappers

For writing kernels and profiling, yes, it's pretty nice. But the host-side API is rather unapproachable. There are, like, 20 API calls just for different variants of memory allocation, all inconsistently named. Also, the APIs are almost entirely (but not 100%) C'ish. In the API wrappers I've written: https://github.com/eyalroz/cuda-api-wrappers I try to address these and some other issues. We should also remember that NVIDIA artificially prevents its profiling tools from supporting OpenCL kernels - with no good reason.

Oh, I really wish those hackers would release the sources rather than pursue their dumbass crypto-mining demands... "We decided to help mining and gaming community" - hurting the gaming community, helping the get-rich-quick "community". My own C++ wrappers for the CUDA APIs (shameless self-plug: https://github.com/eyalroz/cuda-api-wrappers/) would really benefit a lot from behind-the-curtains access to the driver; and even if I just know how the internal logic of the driver and the runtime works, without actually being able to hook into that logic - I would already be able to leverage this somewhat in my design considerations. Also, NVIDIA has definitely had this coming in its choice to promote its own proprietary execution ecosystem (CUDA), rather than build everything up over OpenCL or over both; and in keeping so much of its code clso