Skip to content

V
V8
Switch branch/tag
  1. 19 Jan, 2017 1 commit
  3. 18 Jan, 2017 3 commits
  5. 10 Jan, 2017 1 commit
  7. 09 Jan, 2017 1 commit
  9. 19 Dec, 2016 1 commit
    • yangguo's avatar
      [serializer] do not serialize script wrappers. · 07fa0f49
      yangguo authored 
      The scenario here: the asm function fails asm validation,
so we emit a message. In doing so, we create a JSValue wrapper for
the script object that we cache on the script object. This wrapper
is context-dependent and causes the code serializer to choke.

R=mtrofin@chromium.org, titzer@chromium.org
BUG=chromium:674446,chromium:673321

Review-Url: https://codereview.chromium.org/2586943003
Cr-Commit-Position: refs/heads/master@{#41794}
      07fa0f49
  11. 15 Dec, 2016 1 commit
    • mtrofin's avatar
      [wasm] disable serialization for asm-wasm · 77b50a8e
      mtrofin authored 
      Determine if the scope of the function to be serialized includes asm-
wasm, and if so, bypass serialization, since we do not support it in
that scenario.

In this change, we do so regardless of whether the asm-wasm path was
successful. This is so we keep the design simple, since the guidance
to developers, moving forward, is to use wasm.

BUG=643595

Review-Url: https://codereview.chromium.org/2573193002
Cr-Commit-Position: refs/heads/master@{#41704}
      77b50a8e
  13. 08 Dec, 2016 1 commit
  15. 22 Nov, 2016 1 commit
  17. 21 Nov, 2016 2 commits
  19. 08 Nov, 2016 1 commit
  21. 26 Oct, 2016 1 commit
  23. 19 Oct, 2016 2 commits
    • titzer's avatar
      [wasm] Use a Managed<WasmModule> to hold metadata about modules. · 418b239f
      titzer authored 
      This CL refactors the handling of metadata associated with WebAssembly
modules to reduce the duplicate marshalling of data from the C++ world
to the JavaScript world. It does this by wrapping the C++ WasmModule*
object in a Foreign that is rooted from the on-heap WasmCompiledModule
(which is itself just a FixedArray). Upon serialization, the C++ object
is ignored and the original WASM wire bytes are serialized. Upon
deserialization, the C++ object is reconstituted by reparsing the bytes.

This is motivated by increasing complications in implementing the JS
API, in particular WebAssembly.Table, which must perform signature
canonicalization across instances.

Additionally, this CL implements the proper base + offset initialization
behavior for tables.

R=rossberg@chromium.org,bradnelson@chromium.org,mtrofin@chromium.org,yangguo@chromium.org
BUG=v8:5507, chromium:575167, chromium:657316

Review-Url: https://chromiumcodereview.appspot.com/2424623002
Cr-Commit-Position: refs/heads/master@{#40434}
      418b239f
    • ahaas's avatar
      [turbofan] Use uint32 to store the number of control outputs instead of uint16. · 2f3ca961
      ahaas authored 
      Using uint32 to store the the number of control outputs allows WebAssembly switches to have more than 2^16 case.

BUG=v8:5531
TEST=mjsunit/regress/wasm/regression-5531
R=titzer@chromium.org

Review-Url: https://chromiumcodereview.appspot.com/2425983002
Cr-Commit-Position: refs/heads/master@{#40420}
      2f3ca961
  25. 13 Oct, 2016 2 commits
  27. 07 Oct, 2016 1 commit
  29. 05 Oct, 2016 3 commits
  31. 04 Oct, 2016 1 commit
    • mtrofin's avatar
      [wasm] explicitly mark off unlinked wasm module instances · c938f0df
      mtrofin authored 
      This fixes a gc stress bug. We cannot rely on an ordering of
clearing of the weak cells, so we explicitly reset the weak
link to the owning instance, when finalizing a compiled
module. In turn, this serves as a reliable signal when GCs
happen while instantiating, allowing us to correctly link the
new instance.

BUG=chromium:652425

Review-Url: https://codereview.chromium.org/2393443003
Cr-Commit-Position: refs/heads/master@{#39964}
      c938f0df
  33. 29 Sep, 2016 2 commits
  35. 17 Sep, 2016 1 commit