1. 18 Apr, 2019 13 commits
  2. 17 Apr, 2019 26 commits
  3. 16 Apr, 2019 1 commit
    • Ben Smith's avatar
      [wasm][bulk-memory] Check segment bounds lazily · 34c8443c
      Ben Smith authored
      The bulk memory proposal changed behavior of segment initialization
      during instantiation. Previously, all segments would be bounds-checked,
      after which the segments would be initialized.
      
      The bulk memory proposal removes the up-front check, and always
      initializes active segments in order, starting with element segments and
      then continuing with data segments. Each active segment is initialized
      as-if they were being initialized with the `memory.init` and
      `table.init` instructions, so an out-of-bounds initialization may still
      modify the memory or table partially.
      
      Bug: v8:8892
      Change-Id: I472fca2401e07d60b288f0cc745629a451b31088
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1565033
      Commit-Queue: Ben Smith <binji@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60885}
      34c8443c