KhronosGroup / KhronosGroup/OpenCL-Docs
invariance across calls to geometric functions
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
Creating an issue based on discussion here: https://github.com/KhronosGroup/OpenCL-Docs/issues/1024#issuecomment-1841263676
In the previous discussion we noted that the rounding mode used by a given geometric function is irrelevant as long as the function meets the stated accuracy requirement for the function. However, we also noted that we currently do not have any invariance requirements for geometric functions (or any other functions, really), so it's unclear whether it is allowable to implement a function with one rounding mode one place in the program code, and with a different rounding mode (or any other floating-point configuration?) in a different place in the program code.
Should we have any invariance requirements for geometric functions, or for any other functions for that matter?
Contributor guide
Research direction
The issue identifies no file, test, or entry point. Start with the linked discussion and the existing geometric-function accuracy requirements; define the desired invariance policy and document it in the relevant specification section. Done means the project has an agreed requirement and updated documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100