- 02 May, 2019 1 commit
-
-
Mythri A authored
With bytecode flushing and lazy feedback allocation, we need to call %PrepareForOptimization before we call %OptimizeFunctionOnNextCall Bug: v8:8801, v8:8394 Change-Id: I1f84477a8cef27b4cff61b54daf6fe1a9e5f8e76 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1591775 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61148}
-
- 02 Jun, 2017 1 commit
-
-
Igor Sheludko authored
TBR=machenbach@chromium.org Bug: v8:6457 Change-Id: I75cf773941fc4f3eb6878df14f757ba1d2e23926 Reviewed-on: https://chromium-review.googlesource.com/522647Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#45697}
-
- 30 Jan, 2017 1 commit
-
-
petermarshall authored
Where the arguments have already been inlined, we can replace these calls with a direct call to construct. We have to make sure that the iteration over the arguments is not observable. BUG=v8:5895 Review-Url: https://codereview.chromium.org/2659623002 Cr-Commit-Position: refs/heads/master@{#42765}
-