[Webkit-unassigned] [Bug 165935] New: WebAssembly: When compiling a module we should try to allocate a corresponding Wasm::Memory and put it inside a pool

[bugzilla-daemon at webkit.org]

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

            Bug ID: 165935
           Summary: WebAssembly: When compiling a module we should try to
                    allocate a corresponding Wasm::Memory and put it
                    inside a pool
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sbarati at apple.com
                CC: benjamin at webkit.org, fpizlo at apple.com,
                    ggaren at apple.com, gskachkov at gmail.com,
                    jfbastien at apple.com, keith_miller at apple.com,
                    mark.lam at apple.com, msaboff at apple.com,
                    oliver at apple.com, ticaiolima at gmail.com,
                    utatane.tea at gmail.com

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

-- 
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/20161216/03dfec3e/attachment.html>