Open villekf opened 4 months ago
On (Linux) CUDA machine, the backend returned by af.get_backend() remains at unified even if the backend is correctly set as OpenCL. af.get_active_backend() correctly returns OpenCL as the backend, but since the interoperability functions use different way to check the backend, an error is output (see https://github.com/arrayfire/arrayfire-python/blob/master/arrayfire/opencl.py#L107). Commenting all those instances fixes the issue. The (commented) tests reproduce this error, i.e. https://github.com/arrayfire/arrayfire-python/blob/master/tests/simple/interop.py#L82
af.get_backend()
af.get_active_backend()
Note that this wasn't an issue on a (Windows) AMD machine, where OpenCL is the default backend.
On (Linux) CUDA machine, the backend returned by
af.get_backend()remains at unified even if the backend is correctly set as OpenCL.af.get_active_backend()correctly returns OpenCL as the backend, but since the interoperability functions use different way to check the backend, an error is output (see https://github.com/arrayfire/arrayfire-python/blob/master/arrayfire/opencl.py#L107). Commenting all those instances fixes the issue. The (commented) tests reproduce this error, i.e. https://github.com/arrayfire/arrayfire-python/blob/master/tests/simple/interop.py#L82Note that this wasn't an issue on a (Windows) AMD machine, where OpenCL is the default backend.