<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Implement WebAssembly module parser"
href="https://bugs.webkit.org/show_bug.cgi?id=147293#c31">Comment # 31</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Implement WebAssembly module parser"
href="https://bugs.webkit.org/show_bug.cgi?id=147293">bug 147293</a>
from <span class="vcard"><a class="email" href="mailto:sukolsak@gmail.com" title="Sukolsak Sakshuwong <sukolsak@gmail.com>"> <span class="fn">Sukolsak Sakshuwong</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147293#c30">comment #30</a>)
<span class="quote">> Do we think it is likely that WASM binary format will stay
> little endian?</span >
I'm not sure, but my guess is yes. The design document says "WebAssembly portability assumes that execution environments offer the following characteristics: ... Little-endian byte ordering." <<a href="https://github.com/WebAssembly/design/blob/master/Portability.md">https://github.com/WebAssembly/design/blob/master/Portability.md</a>> So, the little-endian ordering is probably preferred.
<span class="quote">> Would a lot of parsing code have to change if it's
> big endian? It seems like it wouldn't be a lot but I haven't read
> all the WASM code you've been working on.</span >
The final format will likely be very different from what we are using. So, a lot of code will have to change anyway. For the WASMReader class, I think there are only 5 methods would have to change, i.e., int16, int32, int64, float, and double.</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>