diff options
| author | Dan Gohman <sunfish@mozilla.com> | 2017-06-19 13:50:00 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-06-19 13:50:00 -0700 |
| commit | f4a8ea5e844b138ca894eeb875d1d89c5d107127 (patch) | |
| tree | 96b144131d0e36dcff6c88f360d2a853b857aeba /FutureFeatures.md | |
| parent | 79112aed19bd050f9a3e7f43aecfd9a04f040438 (diff) | |
| download | nanowasm-design-f4a8ea5e844b138ca894eeb875d1d89c5d107127.tar.gz | |
Acknolwedge IEEE 754-2018's changes concerning `minNum`/`maxNum`. (#1088)
Diffstat (limited to 'FutureFeatures.md')
| -rw-r--r-- | FutureFeatures.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/FutureFeatures.md b/FutureFeatures.md index 8b4b7d0..a6e3ba0 100644 --- a/FutureFeatures.md +++ b/FutureFeatures.md @@ -312,7 +312,10 @@ use cases: * `f64.fma`: fused multiply-add (results always conforming to IEEE 754-2008) `minnum` and `maxnum` operators would treat `-0.0` as being effectively less -than `0.0`. +than `0.0`. Also, it's advisable to follow the IEEE 754-2018 draft, which has +removed IEEE 754-2008's `minNum` and `maxNum` (which return qNaN when either +operand is sNaN) and replaced them with `minimumNumber` and `maximumNumber`, +which prefer to return a number even when one operand is sNaN. Note that some operators, like `fma`, may not be available or may not perform well on all platforms. These should be guarded by |