Results 1 to 2 of 2

Thread: and header files

  1. #1
    Senior Member
    Join Date
    Mar 2011
    132 and header files

    The file included in OpenCL SDKs for linux from AMD, Intel, and NVIDIA seem to be all different, and similarly so with the header files. It would be nice if Khronos mandated that these be binary equivalent for any given release date (obviously after the release date an update to the current version can't be mandated), or better yet if Khronos made the code open source and kept it updated in the Khronos OpenCL API Registry like the header files. Vendor extensions shouldn't be placed in the official header files until they've been approved by Khronos, and thus available in the official Khronos OpenCL API Registry.

  2. #2
    Junior Member
    Join Date
    Jun 2012

    Re: and header files

    It exists a free OpenCL ICD Loader (ie that should be able to load any ICD (OpenCL implementation). It has been tested with Intel, AMD and NVidia implementations on Linux.

    Do not hesitate to report bug if you find some.

    However, I agree with you that the mess with non standard header files is problematic. Only header files from Khronos should be used and distributed. Private extensions should go into private headers.

Similar Threads

  1. Header files for Kernels
    By clint3112 in forum OpenCL
    Replies: 5
    Last Post: 02-01-2013, 03:33 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
Proudly hosted by Digital Ocean