skip buffer NaN internal representation check this fails on whatever archs having...
authorJérémy Lal <kapouer@melix.org>
Wed, 1 Jan 2025 13:34:52 +0000 (14:34 +0100)
committerJérémy Lal <kapouer@melix.org>
Wed, 1 Jan 2025 13:34:52 +0000 (14:34 +0100)
Last-Update: 2022-05-02
Forwarded: https://github.com/nodejs/node/issues/42945

Gbp-Pq: Topic build
Gbp-Pq: Name skip-buffer-nan-internal-check.patch

test/parallel/test-buffer-writefloat.js

index 8676a819fc776d36d9bb6d71655190f5d5ee18a4..57ec81794a6efd696cdecea9e761b6fef833ba7c 100644 (file)
@@ -53,6 +53,7 @@ buffer.writeFloatLE(NaN, 4);
 
 // JS only knows a single NaN but there exist two platform specific
 // implementations. Therefore, allow both quiet and signalling NaNs.
+/*
 if (buffer[1] === 0xBF) {
   assert.ok(
     buffer.equals(new Uint8Array(
@@ -62,6 +63,7 @@ if (buffer[1] === 0xBF) {
     buffer.equals(new Uint8Array(
       [ 0x7F, 0xC0, 0x00, 0x00, 0x00, 0x00, 0xC0, 0x7F ])));
 }
+*/
 
 assert.ok(Number.isNaN(buffer.readFloatBE(0)));
 assert.ok(Number.isNaN(buffer.readFloatLE(4)));