1. 14 Sep, 2016 1 commit
  2. 13 Sep, 2016 2 commits
  3. 12 Sep, 2016 2 commits
  4. 09 Sep, 2016 1 commit
    • mstarzinger's avatar
      [interpreter] Fix destroyed new.target register use. · 0681deb9
      mstarzinger authored
      This fixes a corner-case where the bytecode was using the <new.target>
      register directly without going through the local variable. The value
      might be clobbered because the deoptimizer doesn't properly restore the
      value. The label will causes bytecode pipeline to be flushed and hence
      ensure {BytecodeRegisterOptimizer} doesn't reuse <new.target> anymore.
      
      R=rmcilroy@chromium.org
      TEST=mjsunit/regress/regress-crbug-645103
      BUG=chromium:645103
      
      Review-Url: https://codereview.chromium.org/2325133002
      Cr-Commit-Position: refs/heads/master@{#39306}
      0681deb9
  5. 08 Sep, 2016 4 commits
  6. 07 Sep, 2016 1 commit
  7. 06 Sep, 2016 2 commits
  8. 05 Sep, 2016 1 commit
  9. 02 Sep, 2016 3 commits
  10. 01 Sep, 2016 3 commits
  11. 31 Aug, 2016 1 commit
  12. 30 Aug, 2016 1 commit
  13. 29 Aug, 2016 1 commit
    • littledan's avatar
      Disallow tail calls from async functions and generators · 5af4cd98
      littledan authored
      Tail calls don't make sense from async functions and generators, as
      each activation of these functions needs to make a new, distnict,
      non-reused generator object. These tail calls are not required per
      spec. This patch disables both syntactic and implicit tail calls
      in async functions and generators.
      
      R=neis
      BUG=v8:5301,chromium:639270
      
      Review-Url: https://codereview.chromium.org/2278413003
      Cr-Commit-Position: refs/heads/master@{#38986}
      5af4cd98
  14. 24 Aug, 2016 2 commits
    • mstarzinger's avatar
      [compiler] Make Compiler::EnsureBytecode not switch tiers. · b52aecac
      mstarzinger authored
      This preserves the original shared code of the underlying function when
      bytecode is provided. The method in question should only ensure bytecode
      is present, but should avoid switching compilation tiers of the given
      function. It might be that the function was fast-tracked to baseline by
      inlining without going through the interpreted tier first.
      
      R=rmcilroy@chromium.org
      TEST=mjsunit/regress/regress-crbug-635923
      BUG=chromium:635923
      
      Review-Url: https://codereview.chromium.org/2278543002
      Cr-Commit-Position: refs/heads/master@{#38866}
      b52aecac
    • bmeurer's avatar
      [turbofan] Use ObjectIsReceiver directly for inlining. · 6646d73b
      bmeurer authored
      Don't bother using %_IsJSReceiver, which immediately gets lowered to
      ObjectIsReceiver anyways (by the JSIntrinsicLowering), but requires
      some complicated rewiring of effect/control chains.
      
      R=mstarzinger@chromium.org
      BUG=chromium:640369
      
      Review-Url: https://codereview.chromium.org/2271973003
      Cr-Commit-Position: refs/heads/master@{#38864}
      6646d73b
  15. 23 Aug, 2016 1 commit
  16. 19 Aug, 2016 1 commit
  17. 18 Aug, 2016 2 commits
  18. 12 Aug, 2016 2 commits
  19. 10 Aug, 2016 1 commit
  20. 09 Aug, 2016 2 commits
  21. 08 Aug, 2016 1 commit
  22. 05 Aug, 2016 4 commits
  23. 04 Aug, 2016 1 commit