From f4a8ea5e844b138ca894eeb875d1d89c5d107127 Mon Sep 17 00:00:00 2001 From: Dan Gohman Date: Mon, 19 Jun 2017 13:50:00 -0700 Subject: Acknolwedge IEEE 754-2018's changes concerning `minNum`/`maxNum`. (#1088) --- FutureFeatures.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'FutureFeatures.md') 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 -- cgit v1.2.3