Skip to content

V
V8
Switch branch/tag
  1. 21 Apr, 2016 1 commit
  3. 14 Apr, 2016 1 commit
  5. 01 Apr, 2016 1 commit
  7. 10 Mar, 2016 1 commit
  9. 09 Mar, 2016 3 commits
  11. 08 Mar, 2016 2 commits
  13. 07 Mar, 2016 1 commit
    • titzer's avatar
      [wasm] Rework encoding of local declarations. · 835c5e6b
      titzer authored 
      Local declarations were previously encoded as an optional set of
4 uint16 values as part of the function declaration. This CL
implements the current design of moving these declarations to
a list of pairs of (type, count) that is part of the body.

R=bradnelson@chromium.org,binji@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1763433002

Cr-Commit-Position: refs/heads/master@{#34564}
      835c5e6b
  15. 03 Mar, 2016 2 commits
  17. 28 Feb, 2016 2 commits
  19. 27 Feb, 2016 2 commits
  21. 19 Feb, 2016 1 commit
  23. 03 Feb, 2016 1 commit
  25. 20 Jan, 2016 1 commit
  27. 08 Jan, 2016 1 commit
    • dtc-v8's avatar
      WASM: Reserve an ignored section for source code meta information. · 0427d9ff
      dtc-v8 authored 
      Requesting reservation of a wasm section for experimentation with
storing source code meta information, such as source code comments,
and also extra inform on presentation of the AST such an `if-block`
pattern being presented as a `when` operation.

The wasm design already defines unrecognized sections to be ignored,
and this reserved section is ignored. This section is only intended to
hold source code meta information and to have no effect on code
execution.

With wasm going live (behind a flag) on v8, I would also like to be
able to give people something to play with in terms of the deployed
binary code being a useful source code. It's all experimental, but I
understand the entire binary format that V8 is currently using is
basically a throwaway, and that the working strategy is to get
something running and then revisit format decisions.

I would like a fixed reserved section number to avoid potential
clashes with other projects - although I am not aware of any other
calls for addition sections beyond the need for debug info. If a fixed
number is not acceptable, then could this patch alternatively ignore
all unrecognized sections and perhaps add the section size to them
all - something which is already noted todo in the design document?

BUG=

Review URL: https://codereview.chromium.org/1565693002

Cr-Commit-Position: refs/heads/master@{#33165}
      0427d9ff
  29. 17 Dec, 2015 1 commit
  31. 11 Dec, 2015 1 commit
    • titzer's avatar
      Initial import of v8-native WASM. · 4c5b3609
      titzer authored 
      As discussed in person, this adds the code from v8-native-prototype into
V8 proper, guarded by GYP flags that do not build the code by default.
Passing wasm=on to 'make' or setting v8_wasm as a GYP flag activates
building of this code.

An additional header file is added to and exported from the compiler
directory, src/compiler/wasm-compiler.h. This exposes a limited interface
with opaque Node and Graph types to the decoder to build TF graphs, as
well as functions to compile WASM graphs.

The mjsunit tests added are blacklisted because they fail without the
WASM object exposed to JS, which is also disabled by the build config
option.

This corresponds closely to https://github.com/WebAssembly/v8-native-prototype/commit/5981e06ebc9b1e578831d03100f17ebb77970ee0, with some formatting fixes and moving some files into src/compiler.

R=mstarzinger@chromium.org, bradnelson@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1504713014

Cr-Commit-Position: refs/heads/master@{#32794}
      4c5b3609