nvidia-opencl-examples VS opencl-intercept-layer

The approach of dynamically loading OpenCL.dll and getting function address to call was proposed by nvidia opencl sdk samples in something like 2009. The original link is https://developer.nvidia.com/opencl but now they are not downloading, but some guys on github have that code samples, for example here https://github.com/sschaetz/nvidia-opencl-examples

Somewhat selfishly, one of the tools I see missing from your guide is the OpenCL Intercept Layer. This is an open-source tool we've developed and we use it every day to debug and analyze OpenCL programs.

I'd also suggest taking a look at the OpenCL Intercept Layer too, if you haven't already. It can do things like logging OpenCL errors, calling clFlush or clFinish after each enqueue, and more, all without modifying source or rebuilding.

The OpenCL Intercept Layer can get it for you (documentation link).

Are you sure your program is executing completely and without errors? I'd strongly recommend using a tool like the OpenCL Intercept Layer to verify that everything is running correctly. You can even it to dump your input and result matrices to verify they are correct, if desired.

We use the OpenCL Intercept Layer extensively. It's open-source, vendor-independent, and cross-platform. I wrote a tutorial to demonstrate common usages, if you want to see what it can do.

At some risk of redundancy, the one tool I would definitely recommend is the OpenCL Intercept Layer, since it will make it a lot easier to debug problems when they inevitably occur, or to optimize your program once it's working. Good luck and have fun!