You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DpCtl implements to various degrees the main SYCL runtime classes (ref Section 4.6.4 of SYCL 2020 spec). We need to add a table in our documentation noting what Sycl functions are supported by dpCtl's C and Python APIs and also noting any limitations or unsupported features.
This information is vital to drive adoption of dpCtl as a Python interface to the core SYCL classes.
Something like:
Class device
SYCL Function
dpCtl C-API function
Python API function
Notes
get_info<info::device::driver_version>
DPCTLDevice_GetDriverInfo
get_driver_version
The text was updated successfully, but these errors were encountered:
diptorupd
changed the title
Add a table in dpCtl's documentation comparing which SYCL classes and functions are supported
Add a table in dpctl's documentation comparing which SYCL classes and functions are supported
Apr 16, 2021
Closing as maintaining such a table manually is extremely cumbersome and fragile. Instead, docstrings for libsyclinterface and Python functions should have a link to the parent sycl function specification. I will open a separate ticket for that purpose (#742).
DpCtl implements to various degrees the main SYCL runtime classes (ref Section 4.6.4 of SYCL 2020 spec). We need to add a table in our documentation noting what Sycl functions are supported by dpCtl's C and Python APIs and also noting any limitations or unsupported features.
This information is vital to drive adoption of dpCtl as a Python interface to the core SYCL classes.
Something like:
Class
device
get_info<info::device::driver_version>
DPCTLDevice_GetDriverInfo
get_driver_version
The text was updated successfully, but these errors were encountered: