Skip to content
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

Introduction of release notes and applied resolved comments in #2052 #2068

Merged
merged 26 commits into from
Feb 20, 2025

Conversation

timmiesmith
Copy link
Contributor

Reopening PR for 2022.8 release notes.

Copy link
Contributor Author

@timmiesmith timmiesmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capturing open notes from the close of #2052

@timmiesmith
Copy link
Contributor Author

The changes brought over from #2052 include changes to address #1912 and #2011

timmiesmith and others added 2 commits February 14, 2025 15:43
Co-authored-by: Dmitriy Sobolev <[email protected]>
@akukanov
Copy link
Contributor

Looks good to me overall.

@timmiesmith timmiesmith dismissed dcbenito’s stale review February 20, 2025 14:33

All changes requested in the review have been made.

akukanov
akukanov previously approved these changes Feb 20, 2025
Copy link
Contributor

@danhoeflinger danhoeflinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@timmiesmith timmiesmith merged commit 11c7b18 into main Feb 20, 2025
2 checks passed
@timmiesmith timmiesmith deleted the 2022-8-release-notes branch February 20, 2025 19:25
timmiesmith added a commit that referenced this pull request Feb 20, 2025
---------
Co-authored-by: Matthew Michel <[email protected]>
Co-authored-by: Dmitriy Sobolev <[email protected]>
Co-authored-by: Alexey Kukanov <[email protected]>
Co-authored-by: Matthew Michel <[email protected]>
Copy link
Contributor

@dcbenito dcbenito left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have some minor final changes. Otherwise LGTM.

with device policies for large data sizes.
- Improved performance of ``copy``, ``fill``, ``for_each``, ``replace``, ``reverse``, ``rotate``, ``transform`` and 30+
other algorithms with device policies on GPUs.
- Improved oneDPL use with SYCL implementations other than Intel oneDPI DPC++/C++ compiler.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the compiler name: Intel® oneAPI DPC++/C++ Compiler

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

- Fixed several issues in the ``sort``, ``stable_sort``, ``sort_by_key`` and ``stable_sort_by_key`` algorithms that:

* Allows the use of non-trivially-copyable comparators.
* Eliminates duplicate kernel names
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a period at the end of this bullet.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

----------------------------
New in This Release
^^^^^^^^^^^^^^^^^^^
- Incorrect results may be observed when calling ``sort`` with a device policy on Intel® Arc™ Graphics 140V with data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This instance of the name calls for a lowercase "g" in "graphics". Please update the name to Intel® Arc™ graphics.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

sizes of 4-8 million elements.
- ``sort``, ``stable_sort``, ``sort_by_key`` and ``stable_sort_by_key`` algorithms fail to compile
when using Clang 17 and earlier versions, as well as compilers based on these versions,
such as Intel(R) oneAPI DPC++/C++ Compiler 2023.2.0.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change the (R) to ® for consistency.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

such as Intel(R) oneAPI DPC++/C++ Compiler 2023.2.0.
- When compiling code that uses device policies with the open source oneAPI DPC++ Compiler (clang++ driver),
synchronous SYCL runtime exceptions regarding unfound kernels may be encountered unless an optimization flag is
specified (e.g. ``-O1``) as opposed to relying on the compiler's default optimization level.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change "e.g." to "for example".

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

timmiesmith added a commit that referenced this pull request Feb 20, 2025
#2074)

---------
Co-authored-by: Matthew Michel <[email protected]>
Co-authored-by: Dmitriy Sobolev <[email protected]>
Co-authored-by: Alexey Kukanov <[email protected]>
Co-authored-by: Matthew Michel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants