From 3b72a3fdd3b53b657e35ea0921493b9ab8d49516 Mon Sep 17 00:00:00 2001 From: Brice Videau Date: Tue, 28 Nov 2023 15:03:01 -0600 Subject: [PATCH] Specify the order of operations in the loader regarding `clIcdGetPlatformIDsKHR`, `clIcdGetFunctionAddressForPlatformKHR`, and `clIcdSetPlatformDispatchDataKHR`. --- ext/cl_khr_icd.asciidoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ext/cl_khr_icd.asciidoc b/ext/cl_khr_icd.asciidoc index 42a435ca..3f5d87a7 100644 --- a/ext/cl_khr_icd.asciidoc +++ b/ext/cl_khr_icd.asciidoc @@ -244,6 +244,12 @@ will be managed by the ICD Loader. If the `CL_ICD2_TAG_KHR` tag is present but one of the two functions above is missing, the ICD Loader will ignore the Vendor ICD and continue on to the next. +For ICD 2 compatible implementations, during initialization, after calling +{clIcdGetPlatformIDsKHR} to query the available platforms, the ICD Loader +will, for each platform, query dispatchable entry points using +{clIcdGetFunctionAddressForPlatformKHR} and then set the platform dispatch +data using {clIcdSetPlatformDispatchDataKHR}. + [[cl_khr_icd-new-procedures-and-functions]] === New Procedures and Functions