oneMKL #include <oneapi/mkl.hpp>

hello, i'm windows10, oneapi user.

when i write oneapi code with onemkl, i can't use oneapi::mkl::rng::device namespace. cmakelists.txt include compile options /Qmkl:sequential /Qmkl-ilp64:sequential

https://github.com/oneapi-src/oneMKL/blob/develop/include/oneapi/mkl.hpp https://github.com/oneapi-src/oneMKL/blob/develop/include/oneapi/mkl/rng.hpp in there, header did not include 'rng/device.hpp'.

i just want to know reason.

Jan 19 '24 07:01 tb5874

I'm not familiar with the rng domain but I can see that the example and tests directly include this file as well. Maybe someone from @oneapi-src/onemkl-rng-write can confirm whether this is intentional?

Jul 11 '24 10:07 Rbiessy

@Rbiessy, yes, having a standalone rng/device.hpp is intentional, as we wanted to stress out what device API are a completely different entity and has header-based implementation. So the expectation is that users may independently include rng/device.hpp functionality within sycl kernels and don't need to link to any binaries.

Sep 17 '24 15:09 aelizaro

Closing as there are no issues, this is done by design.

Feb 27 '25 09:02 Rbiessy