- 30 Jan, 2019 1 commit
-
-
Sven Sauleau authored
We noticed that almost every call site were loading both files, the split isn't necessary anymore. In some message tests, removed the absolute line number to allow future changes. Bug: v8:8726 Change-Id: I8527f0a1ecfa685aa01a5e2f5f47ddf1cb13a545 Reviewed-on: https://chromium-review.googlesource.com/c/1446452 Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#59220}
-
- 29 Oct, 2018 1 commit
-
-
Clemens Hammacher authored
The "grow_memory" opcode was renamed to "memory.grow", and the spec repo was updated to use kExprMemoryGrow internally instead of kExprGrowMemory (https://github.com/WebAssembly/spec/pull/720). This CL does the same change for v8. Drive-by: Rename "current_size" to "memory.size", and a minor cleanup in wasm-graph-builder.js to bring it in line with the version in the js-api tests in the spec repo. R=titzer@chromium.org Change-Id: If525dba898b2c248890a616d3392c22b45f698ef Reviewed-on: https://chromium-review.googlesource.com/c/1302057Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57089}
-
- 19 Aug, 2017 1 commit
-
-
Enrico Bacis authored
This CL introduces 8 tests that verify that the effects of a grow_memory instruction executed inside a conditional branch are visible also when the branch is merged. The tests verify the output of the current_memory instruction and the result of loading a variable stored in the grown memory inside the branch in the following cases: * the memory is grown inside the if branch (with no else branch); * the memory is grown inside the if branch (when an else branch exists); * the memory is grown inside the else branch; * the memory is grown by different amount of pages inside both the if and else branches. R=ahaas@chromium.org,clemensh@chromium.org,gdeepti@chromium.org Change-Id: I8127ebdf959eed5b7b5ca5aa6033a7ea41465f32 Reviewed-on: https://chromium-review.googlesource.com/617222Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Enrico Bacis <enricobacis@google.com> Cr-Commit-Position: refs/heads/master@{#47452}
-