Release notes for oneDPL 2022.8.0 #2052
Conversation
| - ``sort``, ``stable_sort``, ``sort_by_key``, ``stable_sort_by_key``, ``partial_sort_copy`` algorithms | ||
| may work incorrectly or cause a segmentation fault when used a device execution policy on a CPU device, | ||
| and built on Linux with Intel® oneAPI DPC++/C++ Compiler and -O0 -g compiler options. | ||
| To avoid the issue, pass ``-fsycl-device-code-split=per_kernel`` option to the compiler. |
There was a problem hiding this comment.
| - ``sort``, ``stable_sort``, ``sort_by_key``, ``stable_sort_by_key``, ``partial_sort_copy`` algorithms | |
| may work incorrectly or cause a segmentation fault when used a device execution policy on a CPU device, | |
| and built on Linux with Intel® oneAPI DPC++/C++ Compiler and -O0 -g compiler options. | |
| To avoid the issue, pass ``-fsycl-device-code-split=per_kernel`` option to the compiler. | |
| - ``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. This issue occurs when the code is built on Linux with the Intel® oneAPI DPC++/C++ Compiler version 2025.0 or earlier, and with the -O0 -g compiler options. To avoid this issue, pass the ``-fsycl-device-code-split=per_kernel`` option to the compiler. |
That issue was fixed in Intel® oneAPI DPC++/C++ Compiler 2025.1. I slightly changed the wording since the original first sentence was becoming too long. Linking #2011.
There was a problem hiding this comment.
If the issue is fixed in the new compiler version but not the old ones, I would move the note to https://uxlfoundation.github.io/oneDPL/introduction.html#known-limitations, to shorten the release notes.
And please split into several lines of reasonable length.
| - The ``oneapi::dpl::experimental::ranges::reverse`` algorithm is not available with ``-fno-sycl-unnamed-lambda`` option. | ||
| - STL algorithm functions (such as ``std::for_each``) used in DPC++ kernels do not compile with the debug version of | ||
| the Microsoft* Visual C++ standard library. | ||
|
|
There was a problem hiding this comment.
There was an issue in 2022.4 release, which still exists:
esimd::radix_sortandesimd::radix_sort_by_keykernel templates fail to compile when a program
is built with -g, -O0, -O1 compiler options.
It was fixed in Rolling 2423.32 driver. Linking #1912.
Let's include it here. It still exists, but with older drivers.
There was a problem hiding this comment.
Same story - perhaps better to keep it as a "permanent" limitation rather than in the release notes.
No description provided.