Jon Leech
Jon Leech
ISTM these should be integrated into the API spec appendices and link to the SPIR-V extensions underlying them from there. If you like I'll do that PR. Also see related...
I don't know what could realistically be done without massive, massive restructuring of the specifications. Most of the OpenCL C functions, and some of the OpenCL APIs as well, are...
From my PoV, there are not multiple workItemFunctions files - there is a single file, and a large number of .htaccess redirects to it for the individual functions described in...
@bashbaug @nikhiljnv with #950 merged, this will have to be rewritten in terms of the new API spec structure and markup. I'm not sure how many more outstanding PRs that...
IME no matter how much automation is thrown at checking markup - Vulkan and OpenXR have quite a few different scripts looking for different point errors - people can always...
(Related example, you might be surprised how many duplicated connectives like 'and and' / 'the the' are to be found in the spec source).
The 'condition' is something OpenCL-specific. The 'depends' was introduced when syncing with the Vulkan scripts and has the same restrictions, it only speaks to extension and core version dependencies.
Ping (edit: @bashbaug - sorry, other Ben with similar handle) since you're handling accepting PRs.
Did you look at #983 as an alternative? If doing this I suggest punting the actual exclusion list into a method of clconventions.py
Tagging in to get notifications, since this feeds into the asciidoc integration work I'm doing.