I haven’t yet had a chance to look at the OpenCL conformance candidate release, mostly because my productive systems here are 64 bits - whereas the drivers and SDK by nVidia is currently limited to 32 bits.
My assumption is that there is nothing like the runtime API provided by OpenCL. Is that right?
Would anyone here consider it useful if nVidia provided a similar (to CUDA) runtime API on top of OpenCL?
OpenCL is almost the same like CUDA but it’s a non proprietary standard supported by other manufactures (ATI, Apple, etc.). The API is also similar to CUDA.
if you like to have an object oriented header file (i assume that this is what you meant with API), look at the khronos webpages
but you have to fix the header file slightly - it does not work due to the inconsistent state between the cl.h file provided by khronos and the opencl reference.
Of course, I understand why this first release looks the way it does… The design avoids having to develop and distribute compiler tools to developers. The OpenCL device code is compiled in the driver transparently, and the host code is all standard C calls to a library. A runtime-like API requires a real toolchain.
Apparently I was mistaken - the Khronos group currently has no plans to provide a higher level / runtime API for OpenCL. So if anybody else wants to have a go, go ahead!