1. 08 May, 2017 2 commits
    • Ross McIlroy's avatar
      Revert "Reland: [TypeFeedbackVector] Store optimized code in the vector" · fd749344
      Ross McIlroy authored
      This reverts commit 662aa425.
      
      Reason for revert: Crashing on Canary
      BUG=chromium:718891
      
      Original change's description:
      > Reland: [TypeFeedbackVector] Store optimized code in the vector
      > 
      > Since the feedback vector is itself a native context structure, why
      > not store optimized code for a function in there rather than in
      > a map from native context to code? This allows us to get rid of
      > the optimized code map in the SharedFunctionInfo, saving a pointer,
      > and making lookup of any optimized code quicker.
      > 
      > Original patch by Michael Stanton <mvstanton@chromium.org>
      > 
      > BUG=v8:6246
      > TBR=yangguo@chromium.org,ulan@chromium.org
      > 
      > Change-Id: Ic83e4011148164ef080c63215a0c77f1dfb7f327
      > Reviewed-on: https://chromium-review.googlesource.com/494487
      > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
      > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45084}
      
      TBR=ulan@chromium.org,rmcilroy@chromium.org,yangguo@chromium.org,jarin@chromium.org
      # Not skipping CQ checks because original CL landed > 1 day ago.
      BUG=v8:6246
      
      Change-Id: Idab648d6fe260862c2a0e35366df19dcecf13a82
      Reviewed-on: https://chromium-review.googlesource.com/498633Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45174}
      fd749344
    • Ross McIlroy's avatar
      Revert "[Interpreter] Transition JSFunctions to call optimized code when possible." · ce899dfd
      Ross McIlroy authored
      This reverts commit ec619cbd.
      
      Reason for revert: Crashing on Canary
      BUG=chromium:718891
      
      Original change's description:
      > [Interpreter] Transition JSFunctions to call optimized code when possible.
      > 
      > Now that the optimized code hangs off the feedback vector, it is possible
      > to check whether a function has optimized code available every time it's
      > called in the interpreter entry trampoline. If optimized code exists, the
      > interpreter entry trampoline 'self-heals' the closure to point to the
      > optimized code and links the closure into the optimized code list.
      > 
      > BUG=v8:6246
      > 
      > Change-Id: If1bd7c555bb0551bfe04b36baa6bcf949604717e
      > Reviewed-on: https://chromium-review.googlesource.com/488026
      > Reviewed-by: Michael Stanton <mvstanton@chromium.org>
      > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#45103}
      
      TBR=rmcilroy@chromium.org,mvstanton@chromium.org
      # Not skipping CQ checks because original CL landed > 1 day ago.
      BUG=v8:6246
      
      Change-Id: Ibda719be90fddf1d116c03a2a0c3018bcbe76018
      Reviewed-on: https://chromium-review.googlesource.com/498632Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45169}
      ce899dfd
  2. 05 May, 2017 4 commits
  3. 04 May, 2017 3 commits
    • bjaideep's avatar
      PPC/s390: Reland: [TypeFeedbackVector] Store optimized code in the vector · d5878122
      bjaideep authored
      Port 662aa425
      
      Original Commit Message:
      
          Since the feedback vector is itself a native context structure, why
          not store optimized code for a function in there rather than in
          a map from native context to code? This allows us to get rid of
          the optimized code map in the SharedFunctionInfo, saving a pointer,
          and making lookup of any optimized code quicker.
      
          Original patch by Michael Stanton <mvstanton@chromium.org>
      
      R=rmcilroy@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      BUG=v8:6246
      LOG=N
      
      Review-Url: https://codereview.chromium.org/2861863003
      Cr-Commit-Position: refs/heads/master@{#45111}
      d5878122
    • Ross McIlroy's avatar
      [Interpreter] Transition JSFunctions to call optimized code when possible. · ec619cbd
      Ross McIlroy authored
      Now that the optimized code hangs off the feedback vector, it is possible
      to check whether a function has optimized code available every time it's
      called in the interpreter entry trampoline. If optimized code exists, the
      interpreter entry trampoline 'self-heals' the closure to point to the
      optimized code and links the closure into the optimized code list.
      
      BUG=v8:6246
      
      Change-Id: If1bd7c555bb0551bfe04b36baa6bcf949604717e
      Reviewed-on: https://chromium-review.googlesource.com/488026Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45103}
      ec619cbd
    • Ross McIlroy's avatar
      Reland: [TypeFeedbackVector] Store optimized code in the vector · 662aa425
      Ross McIlroy authored
      Since the feedback vector is itself a native context structure, why
      not store optimized code for a function in there rather than in
      a map from native context to code? This allows us to get rid of
      the optimized code map in the SharedFunctionInfo, saving a pointer,
      and making lookup of any optimized code quicker.
      
      Original patch by Michael Stanton <mvstanton@chromium.org>
      
      BUG=v8:6246
      TBR=yangguo@chromium.org,ulan@chromium.org
      
      Change-Id: Ic83e4011148164ef080c63215a0c77f1dfb7f327
      Reviewed-on: https://chromium-review.googlesource.com/494487Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
      Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45084}
      662aa425
  4. 03 May, 2017 3 commits
  5. 02 May, 2017 4 commits
  6. 29 Apr, 2017 5 commits
  7. 28 Apr, 2017 4 commits
  8. 27 Apr, 2017 3 commits
  9. 26 Apr, 2017 6 commits
  10. 25 Apr, 2017 6 commits