1. 30 Jan, 2019 1 commit
  2. 29 Oct, 2018 1 commit
  3. 17 Oct, 2017 1 commit
  4. 18 Apr, 2017 1 commit
    • gdeepti's avatar
      [wasm] Handle no initial memory case correctly when memory is exported · 78b8d7ed
      gdeepti authored
      Currently when the module has memory specified in the compiled bytes, but with no initial memory
      exported memory assigns a bogus buffer to the instance. When grow_memory is called on this buffer, it tries to patch an incorrect address.
       - Fix exported memory to handle no initial memory
       - Fix grow_memory to handle uninitialized buffers
      
      BUG=chromium:710844
      R=bradnelson@chromium.org
      
      Review-Url: https://codereview.chromium.org/2820223002
      Cr-Commit-Position: refs/heads/master@{#44671}
      78b8d7ed
  5. 27 Mar, 2017 1 commit
  6. 12 Dec, 2016 1 commit
    • clemensh's avatar
      [wasm] Generate correct locations for error messages · 222541df
      clemensh authored
      The current logic in Isolate::GetLocationFromStackTrace just ignores
      wasm frames, making the computed location point to the first javascript
      frame, like this:
      
      test.js:17: RuntimeError: divide by zero
      module.exports.main();
                     ^
      RuntimeError: divide by zero
          at main (<WASM>[1]+5)
          at test.js:17:16
      
      This CL not only fixes the location to point to the top-most wasm
      frame, but also exposes to the embedder that the script of that location
      is a wasm script, allowing for custom printing of wasm locations.
      The Shell::ReportException method now checks for this flag, and prints
      wasm locations like this:
      
      <WASM>[0]+5: RuntimeError: divide by zero
      RuntimeError: divide by zero
          at main (<WASM>[0]+5)
          at test/message/wasm-trap.js:15:16
      
      R=titzer@chromium.org, yangguo@chromium.org
      BUG=chromium:613110
      
      Review-Url: https://codereview.chromium.org/2563673002
      Cr-Commit-Position: refs/heads/master@{#41640}
      222541df
  7. 21 Nov, 2016 1 commit
  8. 13 Oct, 2016 2 commits
  9. 05 Oct, 2016 3 commits