OpenCL extension specification template. Revision $Revision: 10641 $ last modified on $Date: 2010-03-10 00:30:25 -0800 (Wed, 10 Mar 2010) $. An extension specification is a (usually) plain text file containing a series of sections describing different aspects of the extension. Fields to be filled in for an actual extension specification are described in the text in following each section header. For an example of a published extension following this template, see http://www.khronos.org/registry/cl/extensions/khr/cl_khr_gl_sharing.txt ---------------------------- TEMPLATE STARTS HERE ---------------------------- XXX - Not complete yet!!! Name Strings _ where is "khr" for a Khronos-approved extension, a vendor tag for a single-vendor extension, and "ext" for a multivendor (but not Khronos-approved) extension. Use the same prefix as for other Khronos API extensions, such as OpenGL. Precedent suggests that the vendor/multivendor tags should be lowercase for OpenCL even though they're uppercase for all other APIs.> Contributors Contact IP Status Version Number <"TBD" until the extension is completed and posted to the Khronos Registry> Status Extension Type Dependencies _". Also describe which release of the OpenCL specification document this extension is written against.> Overview Header File New Procedures and Functions as in the extension name, but the should be uppercase instead of lowercase, e.g. "clNewFunctionKHR".> New Tokens as new entry points. Precede tokens by a summary of which functions they are used in and how. Examples: Returned by clCreateContext when an invalid OpenCL context is specified in properties: CL_INVALID_GL_CONTEXT_KHR 0x???? Accepted as the argument of clGetGLContextInfoKHR: CL_CGL_CURRENT_DEVICE_FOR_GL_CONTEXT_KHR 0x???? > Additions to Chapter NNN / Appendix AAA of the OpenCL Specification Interactions with other extensions _" followed by a summary of the interaction.> Issues Sample Code Conformance Tests Revision History