Skip to content

[oneDPL][doc] Know limitations: a minor change proposed #2208

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[oneDPL][doc] Know limitations: a minor change proposed #2208

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion documentation/library_guide/introduction.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ Known Limitations
* For ``max_element``, ``min_element``, ``minmax_element``, ``partial_sort``, ``partial_sort_copy``, ``sort``, ``stable_sort``
the dereferenced value type of the provided iterators should satisfy the ``DefaultConstructible`` requirements.
* For ``remove``, ``remove_if``, ``unique`` the dereferenced value type of the provided
iterators should be ``MoveConstructible``.
iterators should be ``CopyConstructible``.
Copy link
Contributor

@akukanov akukanov May 6, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

Could you please point out to the place(s) in the code where copy construction is needed?

* When compiling with ``-O0 -g`` options on Linux with the Intel® oneAPI DPC++/C++ Compiler version 2025.0 or earlier
the ``sort``, ``stable_sort``, ``sort_by_key``, ``stable_sort_by_key``, and ``partial_sort_copy`` may work incorrectly
or cause a segmentation fault when used with a device execution policy on a CPU device. To avoid this issue, pass the
Expand All @@ -177,5 +177,7 @@ Known Limitations
than ``2423.32`` (Rolling) and ``2350.61`` (LTS) is used.
See the `Release Types <https://dgpu-docs.intel.com/releases/releases.html>`_
to find information about the relevant Rolling and LTS releases.
* ``sort``, ``stable_sort``, ``sort_by_key`` and ``stable_sort_by_key`` algorithms with a device policy are still not supported
on Windows with Intel® Arc™ graphics 140V.
Comment on lines +180 to +181
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this a temporary limitation or a "permanent" one? If we expect this to be resolved in reasonable time, the note should go into Release Notes, not into this document.


.. _`SYCL Specification`: https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html