[Webkit-unassigned] [Bug 166486] WebAssembly -> JS: don't do a double entry
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jan 2 17:31:45 PST 2017
https://bugs.webkit.org/show_bug.cgi?id=166486
--- Comment #2 from JF Bastien <jfbastien at apple.com> ---
We should also consider optimizing as discussed here:
> > > > Source/JavaScriptCore/wasm/js/WebAssemblyInstanceConstructor.cpp:90
> > > > + // Always start with a dummy Memory, so that wasm -> wasm thunks avoid checking for a nullptr Memory when trying to set pinned registers.
> > > > + Wasm::Memory memory;
> > > > + instance->setMemory(vm, JSWebAssemblyMemory::create(vm, exec->lexicalGlobalObject()->WebAssemblyMemoryStructure(), WTFMove(memory)));
> > >
> > > This makes me wonder if we're better off just having the callee instead of
> > > caller generate a wasm->wasm call thunk. Maybe we should do that in a later
> > > patch, or at least have a bug open to consider it.
> >
> > Yeah I guess we could have an off-to-the-side entrypeint from "other wasm",
> > in addition to the regular "entry from this wasm instance", for all of the
> > exported functions. We'd need to also change the callee codegen, but then we
> > wouldn't need to tail (or rather, we'd inline that tail).
> >
> > That could be more efficient.
> Yeah, let's open a bug and deal with it later.
--
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/20170103/864404ab/attachment-0001.html>
More information about the webkit-unassigned
mailing list