Bufferobject field write sign handling issues on an exotic old ARM platform #336
This issue is limited to an exotic older ARM platform. Due to float-integer cast bugs in the platform, casting a double to an integer doesn't always work correctly. Here's an example what happens with Node.js Buffer binding:
So, 0xdeadbeef gets written as 0x7fffffff, but 0x3eadbeef is written correctly.
This is obviously a platform bug (and a known issue), but I'll try to figure out if this can be accommodated somehow in
Cast issues seem to be surprisingly common in more exotic platforms, so perhaps using a macro to cast from double to various integer types would be appropriate. The cast can often be fixed with inline asm or a C workaround (which is what I've done on this platform previously).
The text was updated successfully, but these errors were encountered: