<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: doesn't with with --useJIT=0"
href="https://bugs.webkit.org/show_bug.cgi?id=168694#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebAssembly: doesn't with with --useJIT=0"
href="https://bugs.webkit.org/show_bug.cgi?id=168694">bug 168694</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><span class="quote">> Why would useJIT()=0 ever be valid with Wasm code? Seems like we should
> never allow running in that configuration since we're already relying on
> JITing for that call IC.</span >
It would be nice to be able to say "compile wasm, but don't JIT JS". I'm not sure what we would call that option. Regardless of what we do, it would:
- AOT wasm (as always)
- Compile the wasm thunks at the same time
- Compile the trampolines that are required for ICs when we compile wasm code (because usually baseline does this?)
I think we might have a super unlikely race in current wasm where it's possible to always be in the interpreter, compile some wasm, and then not have those trampolines either? I'm not sure.</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>