summaryrefslogtreecommitdiff
path: root/test/wasm2js/conversions-modified.2asm.js.opt
diff options
context:
space:
mode:
authorAlon Zakai <azakai@google.com>2020-07-15 11:49:21 -0700
committerGitHub <noreply@github.com>2020-07-15 11:49:21 -0700
commit1c75f7de7e5f93373da34182a8729ace838ef7bd (patch)
treeb5871a574bbfbe1794baa2304809ea9d0b084f97 /test/wasm2js/conversions-modified.2asm.js.opt
parent78e1e5fb58810fcf25ee9192397baa26e3ee017e (diff)
downloadbinaryen-1c75f7de7e5f93373da34182a8729ace838ef7bd.tar.gz
binaryen-1c75f7de7e5f93373da34182a8729ace838ef7bd.tar.bz2
binaryen-1c75f7de7e5f93373da34182a8729ace838ef7bd.zip
Interpreter: Don't change NaN bits when dividing by 1 (#2958)
It's valid to change NaN bits in that case per the wasm spec, but if we do so then fuzz testcases will fail on the optimization of nan:foo / 1 => nan:foo That is, it is ok to leave the bits as they are, and if we do that then we are consistent with the simple and valid optimization of removing a divide by 1. Found by the fuzzer - looks like on x64 on some float32 NaNs, the bits will actually change (see the testcase). I've seen this on two machines consistently, so it's normal apparently. Disable an old wasm spectest that has been updated in upstream anyhow, but the new test here is even more strict and verifies the interpreter literally changes no bits.
Diffstat (limited to 'test/wasm2js/conversions-modified.2asm.js.opt')
0 files changed, 0 insertions, 0 deletions