You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spec it's only stated fmin/fmax satisfies minNum/maxNum in IEEE 754-2008. However IEEE 754-2008 has left the result of minNum(0.0, -0.0) and maxNum(0.0, -0.0) "either 0.0 or -0.0", but Glibc fminimum/fmaximum implementations are already using fmin/fmax and assuming them treating -0.0 as is smaller than 0.0. Thus if an implementation changes the edge-case behavior (note that the change won't violate the currect spec text), Glibc will be blown up.
In the spec it's only stated fmin/fmax satisfies minNum/maxNum in IEEE 754-2008. However IEEE 754-2008 has left the result of minNum(0.0, -0.0) and maxNum(0.0, -0.0) "either 0.0 or -0.0", but Glibc fminimum/fmaximum implementations are already using fmin/fmax and assuming them treating -0.0 as is smaller than 0.0. Thus if an implementation changes the edge-case behavior (note that the change won't violate the currect spec text), Glibc will be blown up.
Similar to #38.
The text was updated successfully, but these errors were encountered: