<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: spec-tests/f32.wast.js fails on ARM64"
href="https://bugs.webkit.org/show_bug.cgi?id=169722#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: spec-tests/f32.wast.js fails on ARM64"
href="https://bugs.webkit.org/show_bug.cgi?id=169722">bug 169722</a>
from <span class="vcard"><a class="email" href="mailto:jfbastien@apple.com" title="JF Bastien <jfbastien@apple.com>"> <span class="fn">JF Bastien</span></a>
</span></b>
<pre>I looked into this and it seems related to NaN handling. The spec tests try to validate NaNs are handled properly and compare their values.
The bug could be:
- In our code
- In the spec tests (they're not currently up to date, see <a href="https://github.com/WebAssembly/spec/pull/414">https://github.com/WebAssembly/spec/pull/414</a>)
- In the code that translates .wast -> .wast.js
This is unlikely to be important for the near future, so I'll ignore it for now. Maybe we can just comment out the "assert_[0-9]+" invocations for now, and revisit when we update the tests.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>