New entry points should not be queried through `clGetExtensionFunctio…

…nAddress`.
KhronosGroup · Dec 5, 2023 · f6c5227 · f6c5227
1 parent 278f069
commit f6c5227
Showing 1 changed file with 7 additions and 8 deletions.
diff --git a/ext/cl_khr_icd.asciidoc b/ext/cl_khr_icd.asciidoc
@@ -235,15 +235,14 @@ Vendor ICD extension suffix using {clGetPlatformInfo} with the value
 If any of these steps fail, the ICD Loader will ignore the Vendor ICD and
 continue on to the next.
 
-*New in version 2.0.0*, the ICD Loader will also query the following
-functions through {clGetExtensionFunctionAddress}:
-{clIcdGetFunctionAddressForPlatformKHR} and {clIcdSetPlatformDispatchDataKHR}.
-If these two functions are present and the pointer to
-`clGetPlatformIDs` in the dispatch structure of a platform is set to
+*New in version 2.0.0*, the ICD Loader will also query the following functions
+from the library: {clIcdGetFunctionAddressForPlatformKHR} and
+{clIcdSetPlatformDispatchDataKHR}. If these two functions are present and the
+pointer to `clGetPlatformIDs` in the dispatch structure of a platform is set to
 `CL_ICD2_TAG_KHR` the platform will be deemed ICD 2 compatible and dispatch
-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.
+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.
 
 [[cl_khr_icd-new-procedures-and-functions]]
 === New Procedures and Functions