-
Notifications
You must be signed in to change notification settings - Fork 798
[SYCL] Fix get() method for non-opencl backends #3070
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
Conversation
Signed-off-by: Alexander Flegontov <alexander.flegontov@intel.com>
looks good to me, but one of LIT tests fails/throws exception. |
Signed-off-by: Alexander Flegontov <alexander.flegontov@intel.com>
LGTM. These OpenCL-only .get() methods will be removed in SYCL2020 in favor of .get_native().
There is no interop of Level-Zero with OpenCL. The Level-Zero interop with SYCL is through get_native() methods. |
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.
LGTM
Signed-off-by: Alexander Flegontov <alexander.flegontov@intel.com>
Signed-off-by: Alexander Flegontov <alexander.flegontov@intel.com>
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.
LGTM
Signed-off-by: Alexander Flegontov <alexander.flegontov@intel.com>
ping @bader |
Before this patch, if you use non-opencl backend, then get() method returns casted wrapper of the native handle and SYCL user can’t use it in his own code. As the user can't release the returned object, it used to lead to a memory leak.
Since, get() method is applicable only for OpenCL backend, this patch adds an exception for cases when get() method is called for non-opencl backend.
Signed-off-by: Alexander Flegontov alexander.flegontov@intel.com