1. 21 Jun, 2016 4 commits
  2. 20 Jun, 2016 2 commits
    • yangguo's avatar
      Simplify AssemblerPositionsRecorder. · 9c3d730d
      yangguo authored
      R=bmeurer@chromium.org, jgruber@chromium.org
      
      Review-Url: https://codereview.chromium.org/2072963003
      Cr-Commit-Position: refs/heads/master@{#37089}
      9c3d730d
    • mtrofin's avatar
      [wasm] Separate compilation from instantiation · c1d01aea
      mtrofin authored
      Compilation of wasm functions happens before instantiation. Imports are linked afterwards, at instantiation time. Globals and memory are also
      allocated and then tied in via relocation at instantiation time.
      
      This paves the way for implementing Wasm.compile, a prerequisite to
      offering the compiled code serialization feature.
      
      Currently, the WasmModule::Compile method just returns a fixed array
      containing the code objects. More appropriate modeling of the compiled module to come.
      
      Opportunistically centralized the logic on how to update memory
      references, size, and globals, since that logic is the exact same on each
      architecture, except for the actual storing of values back in the
      instruction stream.
      
      BUG=v8:5072
      
      Review-Url: https://codereview.chromium.org/2056633002
      Cr-Commit-Position: refs/heads/master@{#37086}
      c1d01aea
  3. 17 Jun, 2016 4 commits
  4. 16 Jun, 2016 3 commits
  5. 15 Jun, 2016 1 commit
  6. 14 Jun, 2016 3 commits
  7. 13 Jun, 2016 1 commit
    • mstarzinger's avatar
      Fix arguments object stubs for large arrays. · e95cfafb
      mstarzinger authored
      This fixes FastNewStrictArgumentsStub and FastNewRestParameterStub to no
      longer assume that the strict arguments object being allocated will fit
      into new-space. The case where said object needs to move to large object
      space is now handled in the runtime.
      
      R=bmeurer@chromium.org
      TEST=mjsunit/regress/regress-crbug-614727
      BUG=chromium:614727
      
      Review-Url: https://codereview.chromium.org/2054853002
      Cr-Commit-Position: refs/heads/master@{#36917}
      e95cfafb
  8. 10 Jun, 2016 1 commit
  9. 09 Jun, 2016 3 commits
  10. 08 Jun, 2016 1 commit
  11. 07 Jun, 2016 1 commit
    • mvstanton's avatar
      Avoid creating weak cells for literal arrays that are empty of literals. · 3cfcc7e1
      mvstanton authored
      It may be that we have a feedback vector, but no literals. In this case
      we can store into the OptimizedCodeMap directly instead of using a WeakCell,
      because all data in the feedback vector is already held weakly.
      
      The use of a WeakCell in the OptimizedCodeMap is only required when
      there are literals which may hold maps strongly.
      
      This is to address a performance regression caused by the creation of
      a large number of WeakCells.
      
      BUG=chromium:615831
      
      Review-Url: https://codereview.chromium.org/2031123003
      Cr-Commit-Position: refs/heads/master@{#36786}
      3cfcc7e1
  12. 06 Jun, 2016 2 commits
  13. 03 Jun, 2016 1 commit
  14. 02 Jun, 2016 1 commit
  15. 01 Jun, 2016 2 commits
  16. 30 May, 2016 1 commit
  17. 27 May, 2016 2 commits
  18. 24 May, 2016 4 commits
  19. 21 May, 2016 1 commit
    • pierre.langlois's avatar
      [ARM64] Make BufferDisassembler print the instruction encoding · 438629ba
      pierre.langlois authored
      This patch changes the disassembly output for ARM64 when tracing
      compiled code. We used to omit printing the encoding as opposed to what
      ARM and X64 do. The new turbolizer tool assumes the encoding is printed
      and gets confused otherwise.
      
      This could have been fixed in the tool instead but making disassembly
      output consistent across architecture seems like a better solution.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/1996983003
      Cr-Commit-Position: refs/heads/master@{#36426}
      438629ba
  20. 19 May, 2016 2 commits