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
  • compiler
  • regress-crbug-1148758.js
Find file
BlameHistoryPermalink
  • Marja Hölttä's avatar
    [super] Fix: receiver can be null / undefined · a07c14f6
    Marja Hölttä authored Nov 19, 2020
    When accessing a super property which is a getter, the receiver
    is not restricted the same way as when doing normal property access.
    
    In particular, the receiver can be null / undefined.
    
    Bug: v8:9237, chromium:1148758, v8:11161
    Change-Id: Ic6bc2053e5d046d4b19e868312aa9b50025256a1
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2549941
    Commit-Queue: Marja Hölttä <marja@chromium.org>
    Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#71281}
    a07c14f6
regress-crbug-1148758.js 704 Bytes
EditWeb IDE

Replace regress-crbug-1148758.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.