Alina Elizarova

Hi @zjin-lcf, thank you for noticing the issue! RocRand is supported with HIPSYCL you can use it right now with a build configuration similar to rocBLAS: ``` # Inside mkdir...

Hi @zjin-lcf , thank you for your interest in oneDPL RNG. For oneDPL you need to call RNG routine to generate every single random number as in C++ standard (or...

Hi @illuhad, thank you for the reply, it is not a high priority as it can have a work-around, just a general alignment with sycl 2020. Another place for example:...

Hi, @Shwetha-Selma, sorry for the delayed responce, I missed this issue. MT2203 generator is not yet available via oneMKL interfaces project, only via [Intel oneMKL ](https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl.html#gs.4rz5f1) and so it can...

@Shwetha-Selma, yes, we plan to extend oneMKL Interfaces with more generators, the ones which are used in DPCT as the first priority, but no exact timeline yet.

Hello, @csccva, I see that you are trying to build Rocrand backend with Intel oneAPI compiler (icpx), but it works only with open source compiler [oneAPI DPC++ Compiler](https://github.com/intel/llvm) or [AdaptiveCpp...

Hi @npolina4, For device API the situation is the following: Intel oneMKL product supports this function and it is available in `#include ` from the [binary distribution](https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl.html#gs.7u02t6) However, we deliberately...

@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...