arrayfire / arrayfire/arrayfire-python

OpenCL interoperability does not work on CUDA machine

未关闭
#267 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
422
派生
63
PR 合并指标
30 天内没有已合并 PR

描述

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

Note that this wasn't an issue on a (Windows) AMD machine, where OpenCL is the default backend.

贡献指南

这个仓库没有索引到贡献指南

调研方向

Start with the backend checks in arrayfire/opencl.py around line 107 and inspect the commented reproduction in tests/simple/interop.py around line 82. Run that interoperability test on a Linux CUDA machine and compare get_backend() with get_active_backend(); done means OpenCL interoperability succeeds without the reported error.

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
backend
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。