Pavel Dyakov
Pavel Dyakov
Hi @spencerpatty, yes, it makes sense to add
@spencerpatty, The proposal sounds great for me. I think it make sense in collaboration between stats and sparse domains on this question. Note: moving layout enum to the mkl namespace...
@spencerpatty, yes, that is the right way here. We can add additional APIs for stats when mkl::layout is introduced. Spencer, am I right that 1.1 spec release is not a...
The failures in testing not related to PR: 1/1 Test #14: sycl_iterator.pass ...............Exit code 0xc0000409 ***Exception: 0.71 sec Cannot load TBB from neither Windows registry key nor CPU runtime configuration...
Hi @AvijitBag07, no updates yet. Please let us know if it blocks your work - we can try to prioritize it
@AvijitBag07, got it, thank you for the feedback. We will increase priority for this engine Just some clarification - we can introduce MT2203 in oneMKL Interfaces, but it won't support...
cuRAND is the Nvidia backend in oneMKL Interfaces. But cuRAND doesn't support MT2203 engine.
@AvijitBag07, do you reference to Device RNG API? If yes, we have a list of engines that is defined in oneMKL spec - https://github.com/uxlfoundation/oneAPI-spec/blob/main/source/elements/oneMKL/source/domains/rng/device_api/device-engines.rst If you are interested in adding...
Intel oneMKL supports MT2203 in Host API only (with x86 CPUs and Intel GPUs as the supported HW). We can add support for MT2203 Host API into oneMKL Interfaces with...
Hi @toxicscum, for RNG we had bug fixes only - no new features