Skip to content

V
V8
Switch branch/tag
  1. 20 Dec, 2016 1 commit
    • clemensh's avatar
      [wasm] Introduce WasmSharedModuleData and refactor other objects · 081ac370
      clemensh authored 
      The new object will hold information which is shared by all clones of a
WasmCompiledModule, e.g. the decoded asm.js offset table, and in the
future also breakpoints. From there, we can set them on each new
instantiation of any clone.

While already changing lots of the code base, I also renamed all
getters from "get_foo" to "foo", to conform to the style guide.

R=titzer@chromium.org, yangguo@chromium.org
BUG=v8:5732

Review-Url: https://codereview.chromium.org/2591653002
Cr-Commit-Position: refs/heads/master@{#41862}
      081ac370
  3. 16 Dec, 2016 1 commit
  5. 15 Dec, 2016 1 commit
  7. 02 Dec, 2016 1 commit
  9. 29 Nov, 2016 1 commit
  11. 28 Nov, 2016 1 commit
  13. 15 Nov, 2016 1 commit
  15. 12 Nov, 2016 1 commit
  17. 11 Nov, 2016 2 commits
  19. 10 Nov, 2016 1 commit
  21. 04 Nov, 2016 1 commit
  23. 31 Oct, 2016 1 commit
  25. 17 Oct, 2016 1 commit
  27. 07 Oct, 2016 2 commits
    • jbroman's avatar
      ValueSerializer: Add more checks before trying to allocate memory for a dense array. · 0004733c
      jbroman authored 
      Found with libfuzzer. The length is automatically converted to int (thus
large sizes could become negative, even though they are legal "array sizes").
Besides that, the length is coerced to a SMI (which is an even tighter
constraint on 32-bit systems, where it limits the legal sizes to 2^30 - 1).

Add checks that the length of a dense array is below that threshold, and also
fail fast if a length that is provided obviously could not be the correct dense
length (because there isn't enough data left in the buffer to populate such an
array).

BUG=chromium:148757

Review-Url: https://codereview.chromium.org/2399873002
Cr-Commit-Position: refs/heads/master@{#40094}
      0004733c
    • jbroman's avatar
      ValueSerializer: Check for no matching ArrayBufferView type being found. · e4cc9557
      jbroman authored 
      Previously this would result in applying trying to find a size modulo zero,
which causes SIGFPE. This approach was preferred over adding a default case
to preserve the ability of the compiler to detect unhandled switch cases
(within the valid range of the enum).

BUG=chromium:148757

Review-Url: https://codereview.chromium.org/2395073003
Cr-Commit-Position: refs/heads/master@{#40088}
      e4cc9557
  29. 06 Oct, 2016 1 commit
  31. 04 Oct, 2016 1 commit
  33. 23 Sep, 2016 1 commit
  35. 17 Sep, 2016 1 commit
  37. 14 Sep, 2016 4 commits
  39. 08 Sep, 2016 1 commit
  41. 07 Sep, 2016 1 commit
  43. 06 Sep, 2016 2 commits
  45. 02 Sep, 2016 1 commit
  47. 30 Aug, 2016 2 commits
  49. 29 Aug, 2016 1 commit
    • jbroman's avatar
      Blink-compatible serialization of array buffer views. · 248f3daf
      jbroman authored 
      The format of this is a little strange, and has to do with the previous
implementation maintaining a "stack" of objects as it works. As a result,
the format writes the array buffer before giving any hint that the reason
for doing so is to obtain a view wrapping it. Handling this without creating
an explicit on-heap stack requires checking whether the next tag is 'V'
after obtaining an array buffer.

BUG=chromium:148757

Review-Url: https://codereview.chromium.org/2287653002
Cr-Commit-Position: refs/heads/master@{#38984}
      248f3daf
  51. 26 Aug, 2016 1 commit
  53. 25 Aug, 2016 1 commit
  55. 24 Aug, 2016 1 commit
  57. 23 Aug, 2016 2 commits
  59. 22 Aug, 2016 1 commit
  61. 19 Aug, 2016 1 commit
  63. 18 Aug, 2016 1 commit