-
Notifications
You must be signed in to change notification settings - Fork 752
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][Docs] Add sycl_ext_oneapi_syclbin extension #16784
Conversation
This commit adds the sycl_ext_oneapi_syclbin for loading a new SYCLBIN file format to `kernel_bundle`. Signed-off-by: Larsen, Steffen <[email protected]>
Signed-off-by: Larsen, Steffen <[email protected]>
Signed-off-by: Larsen, Steffen <[email protected]>
Signed-off-by: Larsen, Steffen <[email protected]>
Signed-off-by: Larsen, Steffen <[email protected]>
---- | ||
!==== | ||
|
||
_Constraints:_ Available only when `State` is not `ext_oneapi_source`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Theoretically, we, Khronos, or someone else may add more states to kernel bundle. We probably need to specify exact states which are allowed here, or otherwise we claim support for every state which can be added in the future.
`bundle_state::object` and any device in `ctxt.get_devices()` does not have | ||
`aspect::online_linker`. | ||
* An `exception` with the `errc::build` error code if `State` is | ||
`bundle_state::object` or `bundle_state::executable`, if the implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should those states be input
or object
? executable
should not require any further processing
This commit adds the sycl_ext_oneapi_syclbin for loading a new SYCLBIN file format to
kernel_bundle
.