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
  • js-api.js
Find file
BlameHistoryPermalink
  • Manos Koukoutos's avatar
    [wasm-gc] Always use JSToWasmObject at the JS-to-Wasm boundary · b5919c41
    Manos Koukoutos authored Sep 07, 2022
    - Remove the {ValueRepr} parameter from Wasm table and global object
      internals. It is now the responsibility of the user to transform
      to/from a JS object. This removes duplicate work in some cases (type
      checking in the caller, transforming in the callee).
    - For the reverse direction in the JS API, introduce
      {WasmObjectToJSReturnValue}.
    
    Bug: v8:7748
    Change-Id: Ie7625cc0f08d38fe74dbe57e69004de2d93b8a11
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3876184Reviewed-by: 's avatarSimon Zünd <szuend@chromium.org>
    Reviewed-by: 's avatarMatthias Liedtke <mliedtke@chromium.org>
    Commit-Queue: Manos Koukoutos <manoskouk@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#83031}
    b5919c41
js-api.js 36.5 KB
EditWeb IDE

Replace js-api.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.