ROCm / ROCm/FlyDSL

FlyDSL Development Roadmap (v0.2)

Open
#631 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

FlyDSL Development Roadmap (v0.2)

Modeled on the SGLang AMD roadmap (sgl-project/sglang#23494). Milestone: v0.2 · due 2026-05-15 · ✓ released.

Contributions and feedback are welcome.

FlyDSL (Flexible LaYout DSL) is the Python front-end of the project. Legend: ✓ done · ▶ in progress · ○ planned.

Focus

  • Layout algebra core: A complete, composable layout algebra as the foundation for all codegen.
  • Codegen on layout algebra: GEMM and MHA built directly on the algebra.
  • Multi-vendor runtime: A clean runtime and Python registration build layout.

Feature and Performance Improvements (v0.2 delivered)

  • Layout algebra & ast_writer
    PoC: @coderfeli @sjfeng1999
    Goal: Full layout algebra plus a better AST writer.

    • ✓ Full layout algebra
    • ✓ Better ast_writer — lower dynamic control flow in external helper functions #452
  • GEMM & MHA
    PoC: @coderfeli
    Goal: GEMM and attention on top of the layout algebra.

    • ✓ GEMM based on layout algebra
    • ✓ MHA support
  • Runtime & packaging
    PoC: @coderfeli
    Goal: Multi-vendor runtime, clean symbol isolation, working install.

    • ✓ Multi-vendor runtime & Python registration build layout (RFC #320)
    • ✓ Hide LLVM/MLIR symbols to co-exist with other MLIR libs #104
    • ✓ CentOS install fix #396 · quickstart vecAdd segfault #286

Next: v0.3 roadmap. All milestones: https://github.com/ROCm/FlyDSL/milestones

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.

Research direction

Read the v0.2 roadmap in this issue and compare its completed items with milestone v0.2. There is no unfinished implementation task described here; the issue points to the v0.3 roadmap in #632 as the next work, so completion is not defined for a new contributor.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.