KhronosGroup / KhronosGroup/GLSL
Operating on 8/16-bit data types inside compute shaders
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 458
- Forks
- 114
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
When enabling extensions that support 8-bit and 16-bit int and float data
types in compute shaders, a warning is given that the respective extension
is not supported in compute shaders and an error will be generated if any of
its types or functions is used. What is the reason for not allowing these
extensions in compute shaders particularly?
Such extensions are GL_EXT_shader_explicit_arithmetic_types
and GL_EXT_shader_16bit_storage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's references to GL_EXT_shader_explicit_arithmetic_types and GL_EXT_shader_16bit_storage, together with the compute-shader restrictions they describe. Done means documenting a clear rationale for the restriction or identifying the specification text that needs clarification; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100