[pypy-dev] More strategies

Armin Rigo arigo at tunes.org
Thu Nov 14 21:55:23 CET 2013


Hi Eli,

On Thu, Nov 14, 2013 at 9:31 PM, Eli Stevens (Gmail)
<wickedgrey at gmail.com> wrote:
> From http://en.wikipedia.org/wiki/NaN#Encoding :
>
> "The state/value of the remaining bits (i.e. other than the ones used
> to identify a NaN as NaN, including the quiet/signaled bits) are not
> defined by the standard except that they must not be all zero. This
> value is called the 'payload' of the NaN. If an operation has a single
> NaN input and propagates it to the output, the result NaN's payload
> should be that of the input NaN. If there are multiple NaN inputs, the
> result NaN's payload should be from one of the input NaNs; the
> standard does not specify which."

Thanks!  That's enough to convince me that we need to be extremely
careful about NaN bits.  For what it's worth, that's not enough to
make us give up on the idea of lists-of-floats-or-ints :-)


A bientôt,

Armin.


More information about the pypy-dev mailing list