Skip to content
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] Relax kernel bundle device check to allow descendent devices #7334

Merged
merged 2 commits into from
Nov 17, 2022

Conversation

sergey-semenov
Copy link
Contributor

Change kernel_bundle_impl constructors to treat descendent devices of context members as valid in accordance with SYCL 2020.

@aelovikov-intel
Copy link
Contributor

Is this related to oneapi-src/oneDPL#657 and KhronosGroup/SYCL-Docs#313 ?

Change kernel_bundle_impl constructors to treat descendent devices
of context members as valid in accordance with SYCL 2020.
@sergey-semenov sergey-semenov marked this pull request as ready for review November 16, 2022 13:25
@sergey-semenov sergey-semenov requested a review from a team as a code owner November 16, 2022 13:25
@sergey-semenov
Copy link
Contributor Author

Is this related to oneapi-src/oneDPL#657 and KhronosGroup/SYCL-Docs#313 ?

Looks related, but the discussion in the docs issue seems to be revolving around the question of passing a root device kernel bundle to a sub-device queue rather than whether descendent devices of context members can be passed along with that context to the kernel bundle constructor. The latter is explicitly stated in the spec when it lists exception cases for get_kernel_bundle:

An exception with the errc::invalid error code if any of the devices in devs is not one of devices contained by the context ctxt or is not a descendent device of some device in ctxt

Copy link
Contributor

@againull againull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@againull againull merged commit a782779 into intel:sycl Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants