ROCm/rocm-systems

ROCm Systems is a "super-repo" that gathers ROCm system-level projects — HIP runtime pieces, hardware query and management libraries, profiling/tracing tools, debug agents, and media libraries such as rocdecode and rocjpeg — under one tree, initially focused on what is needed to build PyTorch. It is aimed at people building or maintaining AMD GPU software stacks rather than at end users running models.

How it changes a workflow

Previously each component lived in its own GitHub repository and shipped as its own package. The repository now lists most components as Completed, meaning the super-repo is the source of truth and the old repository may still be used for releases. Projects marked In Progress ask contributors not to open new pull requests against the individual repo, while Pending projects still use their own repo as the source of truth README. The repository layout is projects/<name> for each former standalone project, plus shared/ for code used as a dependency by several projects that does not produce its own packages README.

Unified build and test workflows, shared tooling, and a single contributor path are the stated goals. Per-component CI badges, and a separate multi-component test workflow built on TheRock, illustrate how integration is checked TheRock workflow. Names were normalized to match released package casing and punctuation, so paths and component names differ from the legacy repos.

Getting started

The README does not give build commands; it points to CONTRIBUTING.md for setup, sparse-checkout configuration, the development workflow, and pull request guidance CONTRIBUTING. Sparse checkout matters here because a single clone would otherwise bring in every component. Compatibility with a particular ROCm release, GPU, or operating system is not stated in the supplied material and should be taken from the individual component rather than the root.

Licence and component scope

The root defines no unified licence. Each subproject retains its original licence, declared in a per-directory LICENSE file, while files outside projects/ and shared/ carry their own headers README. Anyone redistributing or vendoring a component must therefore check that component, not the repository as a whole.

What the evidence does not show

The README gives no setup tutorial, installation steps, or stated platform requirements. Status is a migration table, not a guarantee that every component's tests pass. The repository was created in 2025 and had 545 stars and 475 forks at the supplied snapshot; the single recorded trending-board observation (2026-10-29, +0 stars) is not enough to describe growth or momentum.