The Khronos Group - a non-profit industry consortium to develop, publish and promote open standard, royalty-free media authoring and acceleration standards for desktop and handheld devices, combined with conformance qualification programs for platform and device interoperability.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Re: Needed: information about kernel parameters

Re: Needed: information about kernel parameters

Why do you need this? What can you do with it?

Our cluster-wide OpenCL platform handles 3rd-party OpenCL applications, so it has no advance knowledge about kernel arguments and their type (and we do not have our own parser either to try to analyze the kernel source-codes ourselves).

Our implementation of "clSetKernelArg" needs to look at the kernel argument that is supplied by the application, return an appropriate error-code to the calling application if necessary, then convert memory-objects and samplers to its internal representation.

While the platform is operational, it currently needs to rely on dirty and expensive tricks to find the necessary information, and those tricks also happen to differ from one SDK to the next, which is not good at all. We need a simple way, once a program is built (which would generally be on a different computer) to send back information about all its kernel-argument types and sizes to the computer where the application is running.

Re: Needed: information about kernel parameters

Originally Posted by bwatt

Why do you need this? What can you do with it?

It helps greatly when you are creating OpenCL bindings from another language. It provides easier run-time type checking to ensure that a parameter in the language binding is correctly type mapped to a kernel parameter.