[SYCL] Workaround to support any kernel name for the L0 backend #1980
+13
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem is that currently the L0 driver truncates name of the kernel when queried from the L0 driver. Problem comes from specification which allows to accept any kernel name but limits a kernel name which can be returned by the zeKernelGetProperties function. Signed-off-by: Artur Gainullin <[email protected]>
|
@smaslov-intel Could you please review. |
smaslov-intel
approved these changes
Jul 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem is that currently the L0 driver truncates name of a kernel
when queried from the L0 driver. Problem comes from specification which
allows to accept any kernel name but limits a kernel name which can be
returned by the zeKernelGetProperties function.
Signed-off-by: Artur Gainullin [email protected]