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
OpenCL 3 can use the values: CL_DEVICE_UUID_KHR, CL_DRIVER_UUID_KHR and CL_DEVICE_LUID_KHR in calls to clGetDeviceInfo to get UUID and LUID values from OpenCL 3 devices. A UUID is a 16 byte array and a LUID is an 8 byte array.
Currently, UUIDs and LUIDs are both returned as Vec of the equivalent size and can be converted into Uuid an Luid types defined in device.rs. However, it would be more consistent if the Uuid an Luid types were values of the InfoType enum instead of newtypes in device.rs.
It would also be an opportunity to fix the bug in fmt::Display for Uuid!
The text was updated successfully, but these errors were encountered:
OpenCL 3 can use the values:
CL_DEVICE_UUID_KHR
,CL_DRIVER_UUID_KHR
andCL_DEVICE_LUID_KHR
in calls toclGetDeviceInfo
to get UUID and LUID values from OpenCL 3 devices. A UUID is a 16 byte array and a LUID is an 8 byte array.Currently, UUIDs and LUIDs are both returned as Vec of the equivalent size and can be converted into
Uuid
anLuid
types defined indevice.rs
. However, it would be more consistent if theUuid
anLuid
types were values of theInfoType
enum instead of newtypes indevice.rs
.It would also be an opportunity to fix the bug in fmt::Display for Uuid!
The text was updated successfully, but these errors were encountered: