detection of ICD/OpenCL issues about clinfo HOT 6 CLOSED

This is an interesting idea, but it's not trivial to implement. The problem is that there is no (official) way to find which version of OpenCL is supported by the ICD loader (libOpenCL) —the exception being ocl-icd, which provides its own extension to query for the supported profile. Without that, the only way to check for the supported version would be to try and actuallly call a higher-version function, trapping segmentation faults. Not exactly robust …

from clinfo.

This is now implemented in the latest master branch. Heuristics for OpenCL version support by the ICD loader can be improved, but those may be opened as separate enhancement requests.

from clinfo.

the only way to check for the supported version would be to try and actuallly call a higher-version function, trapping segmentation faults. Not exactly robust …

haven't looked at your code yet, but would those DSO pointers not be NULL (invalid) if unsupported ?

from clinfo.

Yes, that's exactly the way I've implemented it in the code: I do a dlsym of a later function and try to guess the supported version from that.

from clinfo.

ok, thanks for clarifying that - I will be testing this with different platforms and report back here.
Thanks also for being so responsive, much appreciated !

from clinfo.

BTW: This may also be helpful to provide even better runtime information, it's a collection of kernels that are known to crash different platforms: https://github.com/eholk/opencl-stress

from clinfo.