OpenCL just like its graphics cousin, is full of extensions leading to multiple code paths, if one wants to take advantage of GPU features.
Also AFAIK there isn't any vendor supporting OpenCL 2.1, which means we are forced to use C or languages with compilers that are able to target C. Including the whole dance of loading, compiling and linking at runtime.
If AMD decides to go HIP only, and given that no mobile OS cares about OpenCL support, then those worries apply to it as well.
Also AFAIK there isn't any vendor supporting OpenCL 2.1, which means we are forced to use C or languages with compilers that are able to target C. Including the whole dance of loading, compiling and linking at runtime.
If AMD decides to go HIP only, and given that no mobile OS cares about OpenCL support, then those worries apply to it as well.