PrivateMemorySpace array fields are being translated to Constant data arrays in OpenCL
OpenCL private arrays are general purpose registers that are privately available for each thread in the compute unit, and as such those values can only be initialized from the kernel code itself, not the host, and they cannot be marked as belonging to the Constant memory space, which is simply wrong. Currently Aparapi v3.0.0 tries to assign initialization values for them from the host and in the Constant memory space, which is completely wrong and can cause some kernels to fail during execution at host OpenCL driver. This needs to be fixed.