Diptorup Deb

The segfault is resulting from a scenario where the test case uses a double precision floating point value that is not supported on ARC. To work around the issue the...

@samaid @oleksandr-pavlyk We have refactored the README. Can you review the latest README and see if the description is better?

@oleksandr-pavlyk @ndgrigorian I will let you judge if any of these suggestions make sense with your overall vision of improved dpctl documentation pages. Feel free to close the issue if...

@oleksandr-pavlyk @ndgrigorian If I am not wrong the libsyclinterface tests do run during the CI build of packages in both public GitHub and Jenkins CI. Can you confirm and close...

@oleksandr-pavlyk Is the issue still relevant? If not I will suggest it to be closed.

@oleksandr-pavlyk is this related to dpctl not providing a requirements.txt?

As a first step I have renamed what was previously called "C API" to `libsyclinterface` that is a internal helper library used by dpctl to get a C API for...

@oleksandr-pavlyk Any thoughts on how the ticket should be addressed? I think it can be expanded and treated as part of overall documentation improvements.

@oleksandr-pavlyk I was thinking of implementing it as follows: In the C API, add a functor that is initialized with a Python callback function and invokes the callback inside a...

@oleksandr-pavlyk I pushed an as yet untested implementation of `DPCTLSyclQueue_Create` to my [WIP branch](https://github.com/diptorupd/dpctl/blob/4cd1aa8caf5ddf9663eed666fcfbabb20e21f888/dpctl-capi/source/dpctl_sycl_queue_interface.cpp#L166) that implements the `async_handler` feature. I expect this function to replace the `DPCTLQueueMgr_GetQueueFromContextAndDevice` function and to...