KhronosGroup / KhronosGroup/OpenCL-Docs
-cl-unsafe-math-optimizations - is it merely an aggregate of three other named options?
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
At: https://registry.khronos.org/OpenCL/specs/unified/html/OpenCL_API.html#compiler-options , as of version v3.1.1, Fri, 22 May 2026 12:00:00 +0000 , it says:
> #### 5.8.6.3. Optimization Options
>
> ...
>
> `-cl-unsafe-math-optimizations`
>
> Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid, (b) may violate the IEEE 754 standard, (c) assume relaxed OpenCL numerical compliance requirements as defined in the unsafe math optimization section of the OpenCL C or OpenCL SPIR-V Environment specifications, and (d) may violate edge case behavior in the OpenCL C or OpenCL SPIR-V Environment specifications. **This option includes the `-cl-no-signed-zeros`, `-cl-mad-enable`, and `-cl-denorms-are-zero` options.**
(emphasis mine.)
It is not clear whether `-cl-unsafe-math-optimizations` includes:
1. _only_ those three option, i.e. it's a shorthand for their combination, or
2. any number of potential options, but always also those three.
please amend the wording to clarify.
Contributor guide
Research direction
Start with the Optimization Options section linked in the issue and locate its source in the OpenCL-Docs repository. Determine whether the sentence means exactly the three named options or guarantees those three while allowing others, then revise the wording and verify the rendered specification makes the scope unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100