Strange behavior of OpenCL atomic add operation?

You are using atom_add, which is an OpenCL 1.0 extension for local memory. Yet you are passing it global memory. Instead, try OpenCL 1.1's atomic_add, which works with global memory.

Querying my CL_DEVICE_VERSION returns OpenCL 1.0, hence I am referring to these specs: link. Atomic are implemented as an extension, my GPU supports the extension "cl_khr_global_int32_base_atomics" therefore I guess I can use atomics only on global memory buffers. Or, at least, also global memory.

Moreover, can I use the atomic_add instruction if only version 1.0 seems to be supported? – Neenster Nov 3 at 19:05 1 The difference between atom_add and atomic_add is NOT that it works on global memory. There are the cl_khr_(global or local)_int(size)_(base or extended)_atomics, and then built in ones.

You will need to enable the global and/or local version for what you need. The atom_* ones are the extensions, and the atomic_ are the built in ones, and also require the pointer to be volatile. – arsenm Nov 4 at 19:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.