Karl, I have solved the problem. It was how I was pulling the command queue. Previously I was pulling from the from context via ocl:
cl_command_queue queue = viennacl::ocl::current_context().get_queue().handle().get(); Instead, I needed to pull directly from the matrix object: cl_command_queue queue = vcl_A.handle().opencl_handle().context().get_queue().handle().get(); The program appears to run without problem now. Regards, Charles On Wed, Aug 17, 2016 at 3:18 PM, Charles Determan <cdeterma...@gmail.com> wrote: > Ok, thanks, I will try asking those with clBLAS (I haven't started messing > with clMAGMA yet until I can get the clBLAS interface working). I will > report back if I manage to solve the problem. > > Regards, > Charles > > On Wed, Aug 17, 2016 at 3:16 PM, Karl Rupp <r...@iue.tuwien.ac.at> wrote: > >> >> Running again and printing the cl_mem objects (from >>> opencl_handle().get()) it appears that the relevant addresses (last >>> three lines) are being used in multiple areas such as 'Writing data'. >>> >> >> this may be the case, yes. >> >> trying dgemm >>> 0xa84df00 >>> 0xa8b4c40 >>> 0xa8b5990 >>> >> >> These are the correct handles. I don't know why clMAGMA complains. >> >> Best regards, >> Karli >> >> >
------------------------------------------------------------------------------
_______________________________________________ ViennaCL-devel mailing list ViennaCL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viennacl-devel
