1. 25 Jul, 2017 3 commits
  2. 24 Jul, 2017 12 commits
  3. 21 Jul, 2017 3 commits
    • Caitlin Potter's avatar
      [interpreter] refactor BuildGeneratorSuspend/Resume into BuildSuspendPoint · 00681326
      Caitlin Potter authored
      Simplify the model for generating Awaits, because the resume point is
      always immediately following the suspend point, and registers used are
      always the same for both operations.
      
      Includes a minor refactoring of BytecodeGenerator::VisitYield() to
      perform iterator result creation before the SuspendGenerator bytecode,
      rather than between SuspendGenerator and Return. This adds a small
      number of bytecodes for each yield.
      
      BUG=v8:2355, v8:5855
      
      Change-Id: I4868b89a6bc1b251f887d2a45890c8fa19f7b089
      Reviewed-on: https://chromium-review.googlesource.com/576286Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
      Commit-Queue: Caitlin Potter <caitp@igalia.com>
      Cr-Commit-Position: refs/heads/master@{#46820}
      00681326
    • Ross McIlroy's avatar
      Revert "[Turbofan] Merged the OSR phase into the graph building phase." · 5d0a4327
      Ross McIlroy authored
      This reverts commit 69c8f16d.
      
      Reason for revert: Causing crashes on Clusterfuzz - http://crbug.com/747154
      
      BUG=chromium:747154
      
      Original change's description:
      > [Turbofan] Merged the OSR phase into the graph building phase.
      > 
      > Now the OSR phase is only used when OSRing from the ast graph builder.
      > When OSRing from Turbofan, the implementation is now in the graph
      > building phase, at the beginning of the VisitBytecode function.
      > We are no longer generating any OSRLoopEntry or OSRNormalEntry nodes,
      > nor nodes for the possible code of the OSRed function which is before
      > the OSRed loops.
      > 
      > The trimming and reducing of the OSR phase is not done either. This
      > change in the way the way the OSR is done enabled to remove the
      > workaround to the bug mentioned below.
      > 
      > Bug: v8:6112
      > Bug: v8:6518
      > Change-Id: I1c9231810b923486d55ea618d550d981d695d797
      > Reviewed-on: https://chromium-review.googlesource.com/543042
      > Commit-Queue: Alexandre Talon <alexandret@google.com>
      > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
      > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#46801}
      
      TBR=rmcilroy@chromium.org,mstarzinger@chromium.org,leszeks@chromium.org,alexandret@google.com
      
      Change-Id: Ifa9bf5d86e888a47cad7fb10446b36fda5029604
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:6112, v8:6518
      Reviewed-on: https://chromium-review.googlesource.com/581288Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46817}
      5d0a4327
    • Ross McIlroy's avatar
      [Compiler] Remove SharedFunctionInfo from ParseInfo. · c179400b
      Ross McIlroy authored
      Removes the SharedFunctionInfo field from the ParseInfo structure. Instead
      require a SharedFunctionInfo to be explicitly passed to ParseFunction.
      Also renames GetUnoptimizedCode to CompileUnoptimizedFunction to make it
      clear it should only be called for non-top-level code.
      
      BUG=v8:5203
      
      Change-Id: Ibce016e6a5290c3685f7f0a2f5fb1eb2df2ffc3b
      Reviewed-on: https://chromium-review.googlesource.com/574589
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46814}
      c179400b
  4. 20 Jul, 2017 15 commits
  5. 19 Jul, 2017 7 commits