Bug 165935 - WebAssembly: When compiling a module we should try to allocate a corresponding Wasm::Memory and put it inside a pool
Summary: WebAssembly: When compiling a module we should try to allocate a correspondin...
Status: RESOLVED DUPLICATE of bug 170628
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-15 17:17 PST by Saam Barati
Modified: 2017-04-07 17:14 PDT (History)
11 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Saam Barati 2016-12-15 17:17:11 PST
That way, we will know if it was able to get the fast or slow memory and we won't have to compile code twice. Obviously there are still some cases where we have to compile code twice, but this will allow us to only compile once for the single Module single Intance use case (and probably others). When we instantiate, we'll just have to be aware that we may have already created a Wasm::Memory
Comment 1 JF Bastien 2017-04-07 17:14:42 PDT

*** This bug has been marked as a duplicate of bug 170628 ***