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
  • wasm
  • gc-js-interop-async.js
Find file
BlameHistoryPermalink
  • Matthias Liedtke's avatar
    [wasm-gc] Basic JS interop handling for wasm objects · 4893b1c0
    Matthias Liedtke authored Sep 16, 2022
    This change tests all JavaScript language constructs and builtins in
    combination with the unwrapped Wasm objects.
    For JavaScript, excluding some basic introspection (e.g.
    `Object.isExtensible`) WebAssembly GC objects are treated opaque.
    They can be passed around freely but don't allow any access to
    properties, elements etc.
    
    This behavior is currently exposed only if the `wasm-gc-js-interop`
    flag is set.
    
    Bug: v8:7748
    Change-Id: If0dc368f99d4097e3eaf53edde4e244e3081e334
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3879616Reviewed-by: 's avatarJakob Kummerow <jkummerow@chromium.org>
    Reviewed-by: 's avatarNico Hartmann <nicohartmann@chromium.org>
    Commit-Queue: Matthias Liedtke <mliedtke@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#83299}
    4893b1c0
gc-js-interop-async.js 2.97 KB
EditWeb IDE

Replace gc-js-interop-async.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.