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
  • regress
  • regress-351624.js
Find file
BlameHistoryPermalink
  • Mathias Bynens's avatar
    [test] Add %PrepareForOptimization to even more tests · c6a16c10
    Mathias Bynens authored Jun 12, 2019
    With bytecode flushing and lazy feedback allocation, we need to call
    %PrepareForOptimization before we call %OptimizeFunctionOnNextCall,
    ideally after declaring the function.
    
    Bug: v8:8801, v8:8394, v8:9183
    Change-Id: I3fb257282a30f6526a376a3afdedb44786320d34
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1648255
    Commit-Queue: Mathias Bynens <mathias@chromium.org>
    Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
    Reviewed-by: 's avatarMythri Alle <mythria@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#62119}
    c6a16c10
regress-351624.js 612 Bytes
EditWeb IDE

Replace regress-351624.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.