commit | 7c5206036085e334782e1dd625c698f40bf5ad95 | [log] [tgz] |
---|---|---|
author | Giuseppe Bilotta <giuseppe.bilotta@gmail.com> | Fri Jan 13 16:02:30 2017 +0100 |
committer | Giuseppe Bilotta <giuseppe.bilotta@gmail.com> | Fri Jan 13 16:02:30 2017 +0100 |
tree | b0e1444665d63a3b1a2add7e97e042789d44dd17 | |
parent | 96cae1ed9868ab4d634551d4e01b25e70d725037 [diff] |
api/cl.xml: missing quote
The OpenCL-Registry repository contains the OpenCL API and Extension Registry, including specifications, reference pages and reference cards, and the enumerant registry. It is also used as a backing store for the web view of the registry at https://www.khronos.org/registry/cl/ ; commits to the master branch of this repository will be reflected there.
In the past, the OpenCL registry was maintained in a public Subversion repository. The history in that repository has not been imported to github, but it is still available at https://cvs.khronos.org/svn/repos/registry/trunk/public/cl/ .
Interesting files in this repository include:
OpenCL enumerants are documented in api/cl.xml . New ranges can be allocated by proposing a pull request to master modifying this file, following the existing examples. Allocate ranges starting at the lowest free values available (search for “Reserved for vendor extensions”). Ranges are not officially allocated until your pull request is accepted into master. At that point you can use values from your assigned range for API extensions.
Extension specification documents can be added by proposing a pull request to master, adding the specification .txt file under extensions//filename.txt . You must also:
Sometimes extension text files contain inappropriate UTF-8 characters. They should be restricted to the ASCII subset of UTF-8 at present. They can be removed using the iconv Linux command-line tool via
iconv -c -f utf-8 -t ascii filename.txt
(see internal Bugzilla issue 16141 for more).
We will be transitioning to an asciidoc-based extension specification format at some point.