KhronosGroup / KhronosGroup/SYCL-Docs
Required Work Group size when bigger than size_t::max?
- Dominant language
- JavaScript
- Stars
- 158
- Forks
- 80
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 5
Description
Look like we have 2 regime
```
0 < Product(size) < max_work_group -> Fail at runtime
numeric_limit:: Fail at compile time.
```
Should we clarify that? Related to `https://github.com/wenju-he/SYCL-CTS/blob/da719ce893298cdcbff26213606d65ca6908e1d3/tests/optional_kernel_features/kernel_features_reqd_work_group_size.cpp`
_Originally posted by @TApplencourt in https://github.com/KhronosGroup/SYCL-Docs/issues/1010#issuecomment-4926863035_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the related test in tests/optional_kernel_features/kernel_features_reqd_work_group_size.cpp and compare its handling of work-group sizes with the two regimes described in the issue. Identify the relevant SYCL documentation requirement and clarify the compile-time versus runtime failure behavior for sizes beyond size_t::max; done means the specification unambiguously describes both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100