-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sycl::devices created via interop API are not uniqued #6055
Comments
Fix proposed here: #6204 |
…evice (#7550) Fixes #6055 for ext_oneapi_cuda backend. Tested with intel/llvm-test-suite#1419. Signed-off-by: JackAKirk <jack.kirk@codeplay.com>
Thanks! |
Reopened this since the fix was only for the cuda backend and opencl behavior is unchanged from the originally reported issue. |
I think that this is fixed by #13483. Tagging @aelovikov-intel to comment here |
I believe I couldn't fix it for OpenCL because there is CPU backend where the number of all potential (sub-)sub-devices is exponential. |
Ok, but it is at least fixed for top-level devices as illustrated by a test you added, right? |
Can't say that I remember, but it definitely looks so based on the changes in the PR. |
Describe the bug
If a device is created via the interop API it will always create a new device_impl even when there already y exist a device_impl with the same backend handle. this issue is not limited to opencl or any device in particular.
To Reproduce
create a file named test.cpp containing
clang++ being the sycl capable compiler
this will hit the assert even thought (in my case the opencl implementation returned the same device handle)
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: