- 16 Apr, 2019 1 commit
-
-
Adam Klein authored
This is a reland of 656f57bd, which was reverted due to Blink test failures. Those failures have been temporarily suppressed. Original change's description: > [wasm] Add off-by-default runtime flag for growing shared memory > > Grow memory isn't ready to ship in M75. > > Bug: v8:8564, chromium:951795 > Change-Id: I75602bce833653b7943f5606236a97ca6dbad5c9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1566239 > Reviewed-by: Ben Smith <binji@chromium.org> > Commit-Queue: Adam Klein <adamk@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60836} Bug: v8:8564, chromium:951795 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Change-Id: If096f76b4d5d1f5cbcb98e9c11a525a540e21f14 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1568125Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#60855}
-
- 15 Apr, 2019 1 commit
-
-
Michael Hablich authored
This reverts commit 656f57bd. Reason for revert: This blocks lkgr advancement/rolling, see https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8-Blink%20Linux%2064/31263. Please fix upstream tests first. Original change's description: > [wasm] Add off-by-default runtime flag for growing shared memory > > Grow memory isn't ready to ship in M75. > > Bug: v8:8564, chromium:951795 > Change-Id: I75602bce833653b7943f5606236a97ca6dbad5c9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1566239 > Reviewed-by: Ben Smith <binji@chromium.org> > Commit-Queue: Adam Klein <adamk@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60836} TBR=binji@chromium.org,adamk@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:8564, chromium:951795 Change-Id: If212f1b21699394b66e9e306d12a3baf37ccf4b6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1565901Reviewed-by: Michael Hablich <hablich@chromium.org> Commit-Queue: Michael Hablich <hablich@chromium.org> Cr-Commit-Position: refs/heads/master@{#60848}
-
- 13 Apr, 2019 1 commit
-
-
Adam Klein authored
Grow memory isn't ready to ship in M75. Bug: v8:8564, chromium:951795 Change-Id: I75602bce833653b7943f5606236a97ca6dbad5c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1566239Reviewed-by: Ben Smith <binji@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#60836}
-
- 18 Mar, 2019 1 commit
-
-
Sven Sauleau authored
According to WebAssembly's thread proposal, the memory type is decided at the Object's creation and don't change over time. When growing a shared memory and the old buffer was marked as shared; setup the new buffer as shared as well. Bug: v8:8564 Change-Id: I7e59071d11b41315429232ae0c90436c6810bd0e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1526012Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Auto-Submit: Sven Sauleau <ssauleau@igalia.com> Cr-Commit-Position: refs/heads/master@{#60312}
-
- 06 Mar, 2019 3 commits
-
-
Deepti Gandluri authored
This is a reland of 80f06d6f Original change's description: > [wasm] Lazy update instances on a shared Memory.Grow > > - Introduce a GROW_SHARED_MEMORY interrupt, and handler > - Memory objects for isolates are updated on a stack check, add > tracking for isolates that hit the stack check > - When enough memory is not reserved ahead of time, fail to grow > - Add tracking for externalized buffers in the MemoryTracker so > that the MemoryTracker will know when backing_stores can be freed. > - For shared buffer, do not always allocate a new buffer when > growing an externalized buffer > > > Change-Id: I9cf1be19f2f165fa6ea4096869f7d6365304c8c4 > Bug: v8:8564 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1472430 > Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> > Reviewed-by: Ben Smith <binji@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60064} Bug: v8:8564 Change-Id: Id0cf8e42a9d54ac702dba351e248a1b92713c98a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1506357Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#60071}
-
Bill Budge authored
This reverts commit 80f06d6f. Reason for revert: failing grow-memory tests Original change's description: > [wasm] Lazy update instances on a shared Memory.Grow > > - Introduce a GROW_SHARED_MEMORY interrupt, and handler > - Memory objects for isolates are updated on a stack check, add > tracking for isolates that hit the stack check > - When enough memory is not reserved ahead of time, fail to grow > - Add tracking for externalized buffers in the MemoryTracker so > that the MemoryTracker will know when backing_stores can be freed. > - For shared buffer, do not always allocate a new buffer when > growing an externalized buffer > > > Change-Id: I9cf1be19f2f165fa6ea4096869f7d6365304c8c4 > Bug: v8:8564 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1472430 > Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> > Reviewed-by: Ben Smith <binji@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60064} TBR=binji@chromium.org,titzer@chromium.org,gdeepti@chromium.org,ahaas@chromium.org Change-Id: I2ed0b59bcbb285b701172b401d606963261d375c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8564 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1506355Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#60068}
-
Deepti Gandluri authored
- Introduce a GROW_SHARED_MEMORY interrupt, and handler - Memory objects for isolates are updated on a stack check, add tracking for isolates that hit the stack check - When enough memory is not reserved ahead of time, fail to grow - Add tracking for externalized buffers in the MemoryTracker so that the MemoryTracker will know when backing_stores can be freed. - For shared buffer, do not always allocate a new buffer when growing an externalized buffer Change-Id: I9cf1be19f2f165fa6ea4096869f7d6365304c8c4 Bug: v8:8564 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1472430 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60064}
-