Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: cl_khr_icd spec

  1. #11
    Junior Member
    Join Date
    Apr 2009
    Posts
    8

    Re: cl_khr_icd spec

    Quote Originally Posted by oddhack
    Quote Originally Posted by Chris244
    Is there a formal cl_khr_icd specification?
    The Khronos Promoters recently ratified the ICD extension specification and it is available in the Registry now.
    Thanks for passing along the new information Jon!

    There are a couple URLs in the spec. Are these public and if so should I be able to browse there with a web browser? When I follow the links I am prompted for a password.
    https://cvs.khronos.org/svn/repos/OpenCL/trunk/icd/
    https://cvs.khronos.org/svn/repos/regis ... HR/drafts/

    In the section "ICD Loader Vendor Enumeration on Windows" the LoadModule function is mentioned. Should this be LoadLibrary?

    After reading the spec I believe that the interop problem I have with AMD and NVIDIA is that the NVIDIA Vendor ICD and the ICD Loader that NVIDIA shipped (in driver version 195.62) use the entry point clIcdDispatchGetPlatformIDsKHR instead of the specified clIcdGetPlatformIDsKHR. This may not be totally unexpected since the NVIDIA implementation predates both the ratified version of the spec and the ratification date, but I am slightly surprised that the conformance would have passed or that a conformant implementation could claim adherence to an unratified Khronos extension.

    So unless I've misunderstood, the next step appears to be for NVIDIA to ship an updated Vendor ICD and ICD Loader that conforms to the ratified spec.

  2. #12
    Member
    Join Date
    Sep 2003
    Location
    Silicon Valley
    Posts
    57

    Re: cl_khr_icd spec

    Quote Originally Posted by Chris244
    There are a couple URLs in the spec. Are these public and if so should I be able to browse there with a web browser?
    No, they are pointers into our internal SVN repository. I've updated the spec to remove those links. I don't know if it's intended for the ICD source to be made publicly available eventually or not, that's up to the WG.

    In the section "ICD Loader Vendor Enumeration on Windows" the LoadModule function is mentioned. Should this be LoadLibrary?
    I'm not sure. If you want to file a bug in the public Khronos Bugzilla I'll see it gets forwarded to the extension authors. I also asked them to poke their heads in on the various message board threads - it is really outside my domain to answer detailed questions about the ICD Windows internals much less the vendor implementation status

    After reading the spec I believe that the interop problem I have with AMD and NVIDIA is that the NVIDIA Vendor ICD and the ICD Loader that NVIDIA shipped (in driver version 195.62) use the entry point clIcdDispatchGetPlatformIDsKHR instead of the specified clIcdGetPlatformIDsKHR. This may not be totally unexpected since the NVIDIA implementation predates both the ratified version of the spec and the ratification date, but I am slightly surprised that the conformance would have passed or that a conformant implementation could claim adherence to an unratified Khronos extension.
    I believe the WG felt a lot of pressure to get this done quickly so it isn't surprising for there to be some teething pains. But the intent is certainly to get it working cleanly and consistently across all the vendor drivers.
    Jon Leech
    EGL & OpenGL Specification Editor / OpenGL ARB Ecosystem TSG Chair / Khronos API Registrar

Page 2 of 2 FirstFirst 12

Similar Threads

  1. CL_DEVICE_GLOBAL_MEM_SIZE less than spec
    By luizdrumond in forum OpenCL
    Replies: 2
    Last Post: 04-15-2013, 11:26 AM
  2. question about 1.0 spec
    By rlei in forum OpenMAX
    Replies: 0
    Last Post: 01-01-1970, 12:00 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •