nan-payload endianness Lassi Kortela (29 Aug 2020 08:21 UTC)
Re: nan-payload endianness Göran Weinholt (29 Aug 2020 14:35 UTC)
Re: nan-payload endianness Marc Nieper-Wißkirchen (29 Aug 2020 14:58 UTC)
Re: nan-payload endianness Wolfgang Corcoran-Mathe (31 Aug 2020 16:02 UTC)
Re: nan-payload endianness John Cowan (30 Aug 2020 01:00 UTC)
Re: nan-payload endianness Marc Nieper-Wißkirchen (30 Aug 2020 08:41 UTC)
Re: nan-payload endianness John Cowan (30 Aug 2020 14:34 UTC)
Re: nan-payload endianness Marc Nieper-Wißkirchen (30 Aug 2020 15:28 UTC)

Re: nan-payload endianness Marc Nieper-Wißkirchen 30 Aug 2020 08:40 UTC

Am So., 30. Aug. 2020 um 03:01 Uhr schrieb John Cowan <xxxxxx@ccil.org>:

> Correct, which means they will never be returned to the user and therefore won't confuse these procedures.  Ideally, nanboxing should only occupy the signaling NaN space and not the quiet NaN space, since 51 > 48 (the number of address bits in a 64-bit x86 or ARM architecture).

The rest of the bits outside the address bit range may be used for tagging,

All that's fine if the following implementation is also possible:

(define (nan-negative? nan) #f)
(define (nan-quiet? nan) #t)
(define (nan-payload nan) 0)
(define (nan=? nan1 nan2) #t)

Marc