Bug 165935
| Summary: | WebAssembly: When compiling a module we should try to allocate a corresponding Wasm::Memory and put it inside a pool | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Saam Barati <saam> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | benjamin, fpizlo, ggaren, gskachkov, jfbastien, keith_miller, mark.lam, msaboff, oliver, ticaiolima, ysuzuki |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=170628 | ||
Saam Barati
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
JF Bastien
*** This bug has been marked as a duplicate of bug 170628 ***