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-1152231.js
Find file
BlameHistoryPermalink
  • Mythri A's avatar
    Update next_enumeration_index_ correctly in ObjectDescriptor · 8ff422ad
    Mythri A authored Dec 11, 2020
    next_enumeration_index is the next free index available to store a
    property. ObjectDescriptor tracks this field while instantiating the
    literal and updates the next_enumeration_index when finalizing the
    instantiation. When adding new properties (named / computed) we were
    updating this value to the current value that is being used instead
    of next free index. This cl fixes it.
    
    Bug: chromium:1152231
    Change-Id: Ica8c36dcabf035db559e29d4573ecd5e53d6062a
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2577463
    Commit-Queue: Mythri Alle <mythria@chromium.org>
    Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#71709}
    8ff422ad
regress-1152231.js 549 Bytes
EditWeb IDE

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