-
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
Added changelog entries for the upcoming 0.16.1 release #1613
Added changelog entries for the upcoming 0.16.1 release #1613
Conversation
Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞 |
CHANGELOG.md
Outdated
|
||
### Changed | ||
|
||
* Changed behavior of ``dpctl.tensor.usm_ndarray.__dlpack_device__`` method to return device id of the parent unpartition device if array is allocated on a sub-device instead of raising an exception: [#1604](https://github.com/IntelPython/dpctl/pull/1604) |
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.
is unpartition
a SYCL term? If not, should be "unpartitioned".
Array API standard conformance tests for dpctl=0.16.0=py310h15de555_34 ran successfully. |
@oleksandr-pavlyk |
Array API standard conformance tests for dpctl=0.16.0=py310h15de555_49 ran successfully. |
usm-ndarray->usm_ndarray Co-authored-by: ndgrigorian <[email protected]>
Array API standard conformance tests for dpctl=0.16.0=py310h15de555_50 ran successfully. |
## [0.16.1] - Apr. XX, 2024 | ||
|
||
This is a bug-fix release, which also provides a change needed by ``numba_dpex`` project to support dispatching kernels | ||
consuming instances of ``sycl::kernel_accessor`` template type. |
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.
s/sycl::kernel_accessor
/sycl::local_accessor
This PR modifies
CHANGELOG.md
file to document changes from 0.16.0 tag to future 0.16.1 tag.The writeup assumes that gh-1612 is merged, so this should only be merged after gh-1612 is in.