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-1110.js
Find file
BlameHistoryPermalink
  • lrn@chromium.org's avatar
    Don't preparse large files to find boundaries of lazy functions. · ebccde15
    lrn@chromium.org authored Nov 25, 2011
    Instead use the preparser inline to parse only the lazy function
    bodies.
    
    This is still disabled for small files.
    More measurements are needed to determine if lazy-compiling small
    sources is worth it.
    
    Review URL: http://codereview.chromium.org/8662037
    
    git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10066 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
    ebccde15
regress-1110.js 1.83 KB
EditWeb IDE

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