On Wednesday, February 13, 2013 9:01:26 AM UTC-5, Brent Baker wrote: > > >> Are you compiling with clang? It has a bug (fixed in HEAD) that >> affects how it represents NaNs. >> >> > Yeah I am compiling with clang, thanks for the heads up: > $ cc -v > Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn) > Target: x86_64-apple-darwin11.4.2 > Thread model: posix >
Just a quick update on this, I tried with the current HEAD of clang and it has fixed the issue with NaN on ia32. *clang -v:* clang version 3.3 (trunk 175057) > var buff = new Buffer(4); > buff.writeFloatLE(NaN, 0); > buff <Buffer 00 00 c0 *7f*> // <--- correct value The version of clang that ships with xcode produces an incorrect value for NaN: *clang -v: *Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn): > var buff = new Buffer(4); > buff.writeFloatLE(NaN, 0); > buff <Buffer 00 00 c0* ff*> // <--- incorrect value > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
