ROCm / ROCm/FlyDSL

SDK-Free Wheel Packaging and Backend Autodetection

Open
#813 0 comments 2 reactions 1 assignee View on GitHub

@sjfeng1999 is already working on this.

Since Jul 7, 2026.

Dominant language
Python
Stars
282
Forks
120
Avg merge
1d 21h
Merged PRs (30d)
67

Description

The original FlyDSL wheel build assumes a ROCm development environment at build time. In particular, the JIT runtime wrapper includes HIP headers, links hip::host / hip::amdhip64, and setup.py later relies on auditwheel repair exclusions to avoid bundling ROCm user-space libraries.

This RFC proposes changing the packaging model so a release builder that has
only:

  1. llvm-project
  2. the FlyDSL source tree

can build a backend-capable wheel without installing ROCm or CUDA SDKs. Vendor driver/runtime dependencies should be resolved lazily on the user's machine.

The same design prepares the codebase for a future dual-backend wheel (rocdl;nvvm)

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.