Add OpenCL 3.0 API clGetKernelSuggestedLocalWorkSizeKHR.

[haonanya]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[haonanya]

@bashbaug , this is for #229, can you please help enable CI? Thanks very much.

[Kerilk]

Thanks for suggesting this change. If we were to consider adding this to the dispatch table, it would first need to be added here:
https://github.com/KhronosGroup/OpenCL-Headers/blob/main/CL/cl_icd.h

Also the print layer code would have to be generated and updated as well.

[Kerilk]

To be completely honest with you, I don't see this change moving further unless KhronosGroup/OpenCL-Docs#1003 is adopted and we do a major release.

[bashbaug]

I don't think we should be doing this. Frankly, I think it was a mistake to put any extension APIs into the OpenCL ICD loader. It is too late to change this for the extension APIs that are already in the ICD loader, because we want to stay compatible, but we shouldn't be doing this for any extension APIs going forward.

See:

OpenCL-ICD-Loader/loader/icd_dispatch.c

Lines 70 to 73 in 229410f

	// Most extensions, including multi-vendor KHR and EXT extensions,
	// do not need to be ICD-aware and do not require any ICD loader
	// modifications. The KHR and EXT extensions below were added for
	// backwards compatibility only.

Instead, to call an extension API an application should query the extension function pointer using clGetExtensionFunctionAddressForPlatform. This can be done "manually" in the application code itself, or it can be done via a helper library, like the one in the OpenCL SDK:

https://github.com/KhronosGroup/OpenCL-SDK/tree/main/lib/src/Extensions

[haonanya]

Thanks @bashbaug and @Kerilk , I will close the PR and issue.