Skip to content

Commit fd0aab5

Browse files
committed
Add -NaN issue
1 parent 4e7b00e commit fd0aab5

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/references/bugs.bib

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -380,3 +380,12 @@ @misc{bug:webkit:53598
380380
year = {2011}
381381
}
382382

383+
@misc{bug:v8:1101,
384+
abstract = {When we execute the following code, we get back 0xfff8000000000000 (-NaN):\n\nvar buf = new Uint8Array(8);\nvar dv = new DataView(buf.buffer);\ndv.setFloat64(0, NaN, true);\nalert(dv.getUint32(4, true).toString(16)); // High 32-bit\nalert(dv.getUint32(0, true).toString(16)); // Low 32-bit\n\n However, if we change NaN to parseFloat("NaN"), we get back the correct value 0x7ff8000000000000 (NaN). In addition, replacing NaN with 0/0 gives us the incorrect value 0xfff8000000000000. The above script works correctly in JSC.},
385+
keywords = {math, javascript, v8, chrome, nan, ieee754, floating-point},
386+
notes = {See also https://bugs.chromium.org/p/chromium/issues/detail?id=71979.},
387+
title = {{NaN is converted to 0xfff8000000000000 (-NaN)}},
388+
url = {https://bugs.chromium.org/p/v8/issues/detail?id=1101},
389+
year = {2011}
390+
}
391+

0 commit comments

Comments
 (0)