Skip to content

Add revision to XML extensions #1161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bashbaug merged 1 commit into from
May 21, 2024
Merged

Add revision to XML extensions #1161

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions api/opencl_architecture.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2263,6 +2263,25 @@ typedef cl_uint cl_version;
((patch) & CL_VERSION_PATCH_MASK))
----

[NOTE]
--
The available version of an extension is exposed to the user via a macro
defined by the OpenCL Headers. This macro takes the format of the uppercase
extension name followed by the `_EXTENSION_VERSION` suffix. For example,
`CL_KHR_SEMAPHORE_EXTENSION_VERSION` is the macro defining the version of the
{cl_khr_semaphore_EXT} extension.

The value of this macro is set to the {cl_version_TYPE} of the extension using
the semantic version of the extension. If no semantic version is defined for
the extension, then the value of the macro is set to `0` to represent semantic
version `0.0.0`.

Applications can use these version macros along with the convience macros
defined in this section to guard their code against breaking changes to the API
of extensions, in particular provisional KHR extensions which have yet to
finalize an API.
--

[[version-name-pairing]]
==== Version-Name Pairing

Expand Down
Loading