Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
V
V8
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Linshizhi
  • V8
  • Repository

Switch branch/tag
  • v8
  • test
  • mjsunit
  • es6
  • call-with-spread.js
Find file
BlameHistoryPermalink
  • Mythri A's avatar
    [Test] Add %PrepareForOptimization in tests · 55e8d613
    Mythri A authored May 01, 2019
    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: 's avatarRoss McIlroy <rmcilroy@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#61148}
    55e8d613
call-with-spread.js 2.31 KB
EditWeb IDE

Replace call-with-spread.js

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.