OpenCL-CLHPP VS opencl-intercept-layer

Khronos has today released the OpenCL 3.0.14 maintenance update that introduces a new cl_khr_command_buffer_multi_device provisional extension that enables execution of a heterogeneous command-buffers across multiple devices. This release also includes significant improvements to the OpenCL C++ Bindings, a new code generation framework for the OpenCL extension headers, and the usual clarifications and bug fixes. The new specifications can be downloaded from the OpenCL Registry.

Please note that OpenCL consists of two parts: host API and a separate language which is used to write kernels (code which is going to be offloaded to devices). OpenCL specification describes host APIs as C-style APIs and that is what implementors has to provide. However, there are number of various libraries which provides bindings for other languages: - C++ - Python - Go - Rust

opencl.hpp from https://github.com/KhronosGroup/OpenCL-CLHPP evolved from the C++ wrapper API that Ben Gaster started at AMD and I continued evolving. That work has continued since. It is a wrapper for the OpenCL runtime API, but the kernel side code is provided as kernel strings or SPIRV blobs through that API.

I was actually writing my own application in C++. I got the OpenCL CLHPP library downloaded. Wish me luck.

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!