1. 18 Apr, 2016 1 commit
  2. 15 Mar, 2016 1 commit
  3. 04 Mar, 2016 1 commit
  4. 22 Feb, 2016 1 commit
    • mbrandy's avatar
      [wasm] Fix linkage for PPC. · edff6e91
      mbrandy authored
      Floating point param and return registers should be within the
      compiler's allocatable set.
      
      TEST=cctest/test-run-wasm-js/Run_Float64Add_jswrapped
      R=titzer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1714223002
      
      Cr-Commit-Position: refs/heads/master@{#34194}
      edff6e91
  5. 18 Feb, 2016 1 commit
  6. 02 Feb, 2016 1 commit
  7. 21 Jan, 2016 1 commit
    • titzer's avatar
      [wasm] Add utilities to print out WASM ast directly from the bytes. · 3b6b8119
      titzer authored
      Motivated by finding a bug in a larger module, this CL adds the ability
      to dump out a byte-by-byte, nested view of the decoded AST. This
      byte-by-byte output uses the opcode enum to make it readable, but is
      suitable for pasting into a byte[] in C or JS and thus making a regression
      test.
      
      Also fix a bug; the case of running out of registers for indirect calls.
      
      R=ahaas@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/1616973004
      
      Cr-Commit-Position: refs/heads/master@{#33442}
      3b6b8119
  8. 05 Jan, 2016 1 commit
  9. 16 Dec, 2015 1 commit
    • ahaas's avatar
      [wasm] Fixed a problem with float32 stack parameters on 32 bit machines. · 13412d66
      ahaas authored
      The code generation for pushing call parameters on the stack does not
      distinguish between float32 and float64 parameters because both are
      stored in the same registers. Therefore float32 parameters require two
      words on the stack.  The wasm linkage, however, only considered one word
      on the stack for float32 parameters, which caused the problem that
      float32 parameters were not located correctly on the stack. I fixed the
      problem by considering two words for float32 parameters on the stack.
      
      R=bradnelson@chromium.org
      
      Review URL: https://codereview.chromium.org/1529773003
      
      Cr-Commit-Position: refs/heads/master@{#32893}
      13412d66
  10. 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