KhronosGroup / KhronosGroup/SYCL-CTS
Conformance report: Include all device aspects
- Dominant language
- C++
- Stars
- 75
- Forks
- 96
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 4
Description
The device information we [currently print](https://github.com/KhronosGroup/SYCL-CTS/blob/3197f433c6cc4a834f73a381df55270346798e05/util/device_manager.cpp#L77) inside conformance reports is rather limited (only whether FP16 and FP64 are supported). We should include all [`device aspects`](https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:device-aspects), and possibly some additional [device information descriptor values](https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#_device_information_descriptors).
Contributor guide
Research direction
Start in util/device_manager.cpp at the linked conformance-report code, then compare its current device information with the SYCL 2020 device-aspects specification. Determine which device aspects, and any additional device information descriptors, should be reported. Done means conformance reports include the requested device information consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100