- 22 Jul, 2016 1 commit
-
-
ritesht authored
Revert "[wasm] Adding a convolution matrix filter test to highlight the performance advantages of JITing" GC-Stress asserts in filter-jit. This reverts commit ccfd224e. BUG=v8:5044 R=bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2168343002 Cr-Commit-Position: refs/heads/master@{#37961}
-
- 21 Jul, 2016 1 commit
-
-
ritesht authored
This cl also fixes two bugs in the previous code: 1) JITed functions were not allowed access to the heap because the module instance wasn't correctly synthesized. This wasn't discovered in the previous test. 2) Decoding of functions with the JITSingleFunction opcode was off by 1 as the length of the opcode wasn't computed correctly. BUG=5044 Review-Url: https://codereview.chromium.org/2168183002 Cr-Commit-Position: refs/heads/master@{#37957}
-
- 14 Jul, 2016 1 commit
-
-
ritesht authored
[wasm] Adding feature to JIT a wasm function at runtime and hook up the compiled code into the indirect function table The runtime JIT function is passed in the function table to hook up the compiled code and the starting address of the memory to locate the bytes to be compiled. BUG=5044 Review-Url: https://codereview.chromium.org/2137993003 Cr-Commit-Position: refs/heads/master@{#37735}
-
- 06 Jul, 2016 1 commit
-
-
mstarzinger authored
This removes explicit uses of the RUNTIME_ASSERT macro from some runtime methods. The implicit ones in CONVERT_FOO_ARG_CHECKED will be addressed in a separate CL for all runtime modules at once. R=titzer@chromium.org BUG=v8:5066 Review-Url: https://codereview.chromium.org/2125793002 Cr-Commit-Position: refs/heads/master@{#37547}
-
- 29 Jun, 2016 1 commit
-
-
gdeepti authored
- Enable grow memory tests on 32 bit windows - Use handles to module JSObject instead of object pointers R=ahaas@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2105013004 Cr-Commit-Position: refs/heads/master@{#37409}
-
- 28 Jun, 2016 2 commits
-
-
mtrofin authored
This reverts commit 1eb1dfab. The original compilation separation change avoided associating a heap for the wasm instance if memory was not provided, nor needed. The grow memory CL assumed the old behavior, where a memory buffer was always present, but may have had a zero size. The 2CLS landed shortly after one another. We decided to treat the grow memory as the race condition winner, so this CL here re-lands compilation separation, plus adjusts grow memory to deal with the undefined mem buffer. BUG= Review-Url: https://codereview.chromium.org/2102193003 Cr-Commit-Position: refs/heads/master@{#37352}
-
gdeepti authored
- GrowMemory runtime function, tests added to checks if memory can be grown and relocation information is updated correctly R=titzer@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2051043002 Cr-Commit-Position: refs/heads/master@{#37338}
-