Correct the docs for WASM relaxed_simd's relaxed_min/relaxed_max operations
#1963
+16
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current doc comments say that these behave like one of two operations:
fmin/fmax, which return NaN if either operand is NaN, and treat -0.0 as less than 0.0 (this corresponds to IEEE754'sminimumandmaximumoperations).fpmin/fpmax, which return the first operand if either operand is NaN, and also returns the first operand if both are ±0.0.These are not the only possibilities, however! The specification says that it can also:
minimumNumberandmaximumNumberoperations).fpmin/fpmaxbut with the operands flipped.I've chosen to just link to the spec; it's easier than trying to explain the precise semantics.