Re: NA & operations with it

[Daniel Kraft]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

On 2013-11-21 15:21, Mike Miller wrote:
>> From a quick glance I think it's because NA is a specific NaN
>> constant
> in liboctave, and -NA changes the sign bit so it is no longer the
> same specific value.
> 
> Best to report a bug so this isn't forgotten, even if you are
> intending to work on it.

reported: https://savannah.gnu.org/bugs/?40668

I think your analysis regarding the sign bit is correct, at least it
seems to be a possible fix to ignore the sign bit in
__lo_ieee_is_NA().  See also the bug report.

I don't know if this is the correct way to fix it, though.  (But it
looks good to me.)

Yours,
Daniel

- -- 
http://www.domob.eu/
OpenPGP: 901C 5216 0537 1D2A F071  5A0E 4D94 6EED 04F7 CF52
- --
Done:  Arc-Bar-Cav-Hea-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Mon-Pri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQJ8BAEBCgBmBQJSj1OsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MDFDNTIxNjA1MzcxRDJBRjA3MTVBMEU0
RDk0NkVFRDA0RjdDRjUyAAoJEE2Ubu0E989SnOIP/31tarGKca/5frOlFGeqKbuR
uRPFPmkdu3tc5H30C9+VAmW6iUrOYHCtwIyZCZsVN1r5YjBt98rgV3M4NTKA8KIu
3GOLnr38YqLOwp/jcENsCuObp8UNqis7jHjSgCiBQHtJdhZBEF6b5i7hiaiHNtyY
qrXG9JEjnHEEKkvlCd7AynwzCxK1DM+dh1BQF12bDvrNeujdVH9TmxO5rcsBZbRj
BErHEbbu31gd1XhcAEQ9aSwd8yc0T4FQb4T2IC2Rj3i0M5g8be5zSONYObiLYli3
h6S4ftwAKd4B8+VxwYv3inEYeKrsVHjSrXxc1zD/731xXiuKXxDwsjCd4k11XJCi
E7JwpFmn6+mLkwD4sLi9Ee06tUsh9aVAsJzegZHZfgekVuQwf+0+vvqcp3AvX/nE
iHZ44Yy3HdRSde8dfxzhvwIed8d1tWpnd3hnqKKzvdpGiDHjZi76E5wI13eMNePv
nX0D5hwjOTMKB8UvFMEfO/k5odbEvXdwA1qmNPybcldKytKtNavQKsDvfaTGH33Z
qsr4rTxwCIz2+/Yp+jbxJYtXpgtsSN9dAHA/TCuveJ6dt84371vL0Ok+zL3UiitG
XiKO/XkqVEkVmrlaRd0GGSQsZ7QAltXQdARg0Af4ln5CozdweLwrB9wflaWEOmK0
LKjrHdKkbuADzeZoUJ37
=98xP
-----END PGP SIGNATURE-----

smime.p7s
Description: S/MIME Cryptographic Signature