-
Notifications
You must be signed in to change notification settings - Fork 739
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
clang version 18.0.0 gives runtime error while creating sycl::queue with sycl::image support #11135
Comments
Hi @Shwetha-Selma, Tagging @steffenlarsen here to comment, but I think that the result is expected: |
Hi @AlexeySachkov Thanks for the reply, changing
|
Tag @ProGTX to help answer the bindless image questions above. |
@ProGTX @steffenlarsen @przemektmalon @Seanst98 Any answers/update for my question? |
Alternatively, tag @przemektmalon | @Seanst98 . |
Hi @Shwetha-Selma, to answer your queries regarding bindless images
I'm not 100% how to interpret this, so please let me know if this answers your query. The Our Bindless Image extension does, however, introduce some aspects of images that were originally in SYCL 1.2.1. E.g., we re-introduce
Bindless images provide support for 1-, 2-, and 4-channel images. |
Hi @Shwetha-Selma, I believe I may be able to help.
SYCL Bindless Images, as outlined in the Experimental Extension Doc, are part of neither legacy 1.2.1 images nor 2020 images. As well, neither of 1.2.1 images nor 2020 images are part of bindless images. As stated in the doc, bindless images are "meant as building blocks for implementing SYCL 2020 images on top of", making bindless images their own type but with there being an influence from 2020 images. If you would like to query for support of SYCL Bindless images, please use
Bindless images support 1, 2, or 4 channel image formats. The specifics can be found in the here, where you'll see that Bindless images have reverted from the SYCL 2020 |
@przemektmalon @isaacault Thanks so much for the detailed answer, it does clear my doubts. |
@Shwetha-Selma, does it mean that we can close the issue? Are there any other questions left unanswered? |
My doubts are clarified. you can close this issue. |
sycl::queue created with
aspect_selector(sycl::aspect::image)
throws runtime error on clang version 18.0.0To Reproduce
terminate called after throwing an instance of 'sycl::_V1::runtime_error' what(): No device of requested type available. -1 (PI_ERROR_DEVICE_NOT_FOUND) Aborted (core dumped)
Expected Output -
Starting...
Creating queue with sycl image support...
Running on NVIDIA H100 PCIe
Environment (please complete the following information):
Target: x86_64-unknown-linux-gnu
Thread model: posix
Additional context
Code gives expected output with clang 17.0.0
clang version 17.0.0 (https://github.com/intel/llvm a7a6de2)
Target: x86_64-unknown-linux-gnu
Thread model: posix
The text was updated successfully, but these errors were encountered: