Tags: uxlfoundation/oneDAL
Tags
Fix *_input classes destructors visibility (#3591) (#3601) Fixes the ABI breakage introduced by CPU SPMD algorithms in the PRs #3507, #3585 Make the binding type of the destructors (~compute_input(), ~partial_compute_input(), ~train_input(), etc.) stably "WEAK" and not dependent on the compiler's logic by adding their non-default implementations. Also fixes `set_responses` method in KNN. (cherry picked from commit 0a5f4cb) Co-authored-by: Victoriya Fedotova <victoriya.s.fedotova@intel.com>
Fix incorrect CPU topology initialization (#3304) (#3487) The error handling in the global object that defines CPU topology in oneDAL/DAAL and in global daal::services::Environment object was improved. Several related bugs were fixed. - cpp/daal/src/services/service_topo.h and cpp/daal/src/services/service_topo.cpp files re-worked to make it less error prone. - The logic in setChkProcessAffinityConsistency() was changed to allow affinity masks that contain zeros. Previously having the process affinity mask with zeros lead to undefined behavior because the global object that defines CPU topology ended up in non-initialized state in that case. - Out-of-bound memory access issues in CPU topology initialization were fixed. - The constructor of daal::services::Environment class was updated to always call getCpuId() method which initializes the Environment instance. Without this call an uninitialized version of Environment might be used. - The behavior of daal::services::Environment::getInstance() function that returns the pointer to a global DAAL's Environment object was changed. Now the function returns nullptr in case the global Environment object is uninitialized. The respective null pointer checks were added into the calling code. - The behavior of daal::services::Environment::initNumberOfThreads() was changed to handle the case of hyper-threading correctly, setting the maximal number of threads available to oneDAL equal to the number of physical CPU cores.
2025.10 deprecations (#3407) This PR adds information about the APIs that are planned to be removed in oneDAL 2026.0. All those APIs are now marked as deprecated in the headers and in the docs. The description of the deprecations added into the documentation: docs/source/deprecation.rst Also: -Wno-deprecated-declarations flag was added into Bazel config, and /wd4996 flag was added to DAAL examples CMake on Windows in order to suppress the deprecation warnings. See the respective RFCS for the details: https://github.com/uxlfoundation/oneDAL/tree/rfcs/rfcs/20251015-DAAL-algorithms-deprecation https://github.com/uxlfoundation/oneDAL/tree/rfcs/rfcs/20251016-DAAL-data-sources-deprecation https://github.com/uxlfoundation/oneDAL/tree/rfcs/rfcs/20251023-DAAL-matrices-deprecation https://github.com/uxlfoundation/oneDAL/tree/rfcs/rfcs/20251022-DAAL-interfaces-deprecation
Support spmd knn search (#3262) * Support spmd knn search * clang * further restriction of responses logic based on result_options * clang * fix event addition * add queue waits for experimentation * trying without split_table * take 2 * revert debugging * address comment * restore last * debugaboo * further debugging * MORE DEBUG * further debugging * more * shared instead of device * revert last and try wait and throw on copy * trying wait_or_pass * push back events * hotfix: working but suboptimal wait_and_throw in loop * remove debug * minor formatting revisions
PreviousNext