[Webkit-unassigned] [Bug 168694] WebAssembly: doesn't with with --useJIT=0

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 21 19:19:32 PST 2017


https://bugs.webkit.org/show_bug.cgi?id=168694

Filip Pizlo <fpizlo at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Filip Pizlo <fpizlo at apple.com> ---
(In reply to comment #2)
> > 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.
> 
> 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.

I don't think useJIT means what you want it to mean.  useJIT determines whether JSC is allowed to JIT.  If it's not allowed to JIT, then it's not allowed to wasm.  The only time we set it to false is to simulate environments where we don't have the JIT entitlement, and so cannot JIT at all.

So I think this is wontfix.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170222/41810700/attachment.html>


More information about the webkit-unassigned mailing list