-
Notifications
You must be signed in to change notification settings - Fork 730
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][Bindless][Doc][ABI-Break] Rename external semaphore destroy to release #14535
[SYCL][Bindless][Doc][ABI-Break] Rename external semaphore destroy to release #14535
Conversation
… release Rename function destroy_external_semaphore to release_external_semaphore. This name change is to clarify exactly what is happening to the external semaphore. That is, it is being released not destroyed.
@@ -1904,16 +1904,16 @@ the `ext_oneapi_signal_external_semaphore` call complete. | |||
are non-blocking, asynchronous operations. | |||
|
|||
The user must ensure to destroy all external semaphore objects once they are no |
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.
The user must ensure to destroy all external semaphore objects once they are no | |
The user must ensure to release all external semaphore objects once they are no |
?
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.
I've updated the wording in the spec as it might cause confusion as to what exactly is being destroyed.
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
@intel/llvm-gatekeepers can we merge this please? The failure in CI is unrelated to this PR. |
Merging, issue seems like an antivirus problem on the runner, not a source problem and we aren't seeing this anywhere else |
Rename function destroy_external_semaphore to release_external_semaphore.
This name change is to clarify exactly what is happening to the external semaphore. That is, it is being released not destroyed.
Corresponding UR PR: oneapi-src/unified-runtime#1855