-
Notifications
You must be signed in to change notification settings - Fork 30
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
Changes the API for DPCTLUSM_GetPointerType. #1061
Conversation
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_77 ran successfully. |
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! Thanks @diptorupd
View rendered docs @ https://intelpython.github.io/dpctl/pulls/1061/index.html |
86be4cf
to
2492420
Compare
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_77 ran successfully. |
50196bc
to
065e28e
Compare
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_77 ran successfully. |
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_78 ran successfully. |
- DPCTLUSM_GetPointerType used to return a global string literal and had an API that is different from all other libsyclinterface functions that return a C string. Returning a pointer to a global literal as opposed to a heap allocated memory meant the ownership of the pointer was not clear when crossing language boundary. Calling DPCTLCString_Delete on the previously returned const char* will cause a segfault - The PR introduces an enum for usm types and returns an enum value from DPCTLUSM_GetPointerType. - All Python API is unaffected.
1310d09
to
e75f13b
Compare
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_77 ran successfully. |
Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞 |
Array API standard conformance tests for dpctl=0.14.1dev1=py310h76be34b_77 ran successfully. |
Have you provided a meaningful PR description?
DPCTLUSM_GetPointerType used to return a global string literal
and had an API that is different from all other libsyclinterface
functions that return a C string.
Returning a pointer to a global literal as opposed to a heap
allocated memory meant the ownership of the pointer was not
clear when crossing language boundary.
Calling DPCTLCString_Delete on the previously returned const char*
will cause a segfault
The PR introduces an enum for usm types and returns an enum value
from DPCTLUSM_GetPointerType.
All Python API is unaffected.
Have you added a test, reproducer or referred to an issue with a reproducer?
Existing unit tests have been updated.
No
Yes