WebAssembly / WebAssembly/wasi-webgpu

Inquiry regarding documentation and status of wasi-gpu for non-browser applications

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
220
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Hi everyone,

I have been working with the WebAssembly Component Model for some time now, specifically using WASI, WIT, and WAC to compose applications written in C and Rust. My current workflow involves running these components via Wasmtime.

I am very interested in extending my current applications to leverage the host's GPU for computational tasks (specifically for kernel execution and performance modeling), but I want to do this strictly in a non-browser/standalone environment.

I noticed this repository is under active development. Could you point me to any available documentation, examples, or even draft WIT files that demonstrate how to grant a component access to the GPU using the current Component Model standards?

Specifically, I am looking for:

  • The recommended way to define GPU requirements in a .wit world.
  • How to link these requirements to the host's native GPU (e.g., using wgpu or wasmtime-gpu) during the composition/instantiation phase.

Thank you for your great work on this specification!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no specific files, tests, or entry points. Start by reviewing the repository's current documentation, examples, and WIT definitions for standalone GPU access, then compare them with the requested Wasmtime or wgpu integration. Done means documenting the current status and providing the requested guidance or examples, if supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, rust, wasm
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.