rocm-libraries

Why the super repo exists

rocm-libraries is a super repository from AMD that consolidates multiple ROCm related libraries and shared components into a single source tree. The README states the goal is to streamline development, continuous integration, and integration work across those libraries. Before this consolidation, each library lived in its own repository with its own build and CI setup, which created duplicated tooling and made cross library work harder. By pulling them together, the project enables unified build and test workflows, shared tooling and contributor experience, and better visibility and collaboration across the ROCm library teams. The practical effect is that a contributor can check out one tree and build or test several libraries at once, rather than cloning many repos and reconciling different systems. This also gives the ROCm team a single place to run multi component testing. The README points to TheRock, a separate build system, as the engine underneath the unified CI, and it shows CI status badges for both the standard and the nightly TheRock pipelines. For someone outside AMD, the value is simpler: one repository to watch for a large slice of the ROCm math and runtime libraries, with a consistent way to build them. For downstream packagers the single tree also reduces the chance of version mismatches between libraries that used to ship on independent schedules.

Migration status of components

A large part of the README is a table tracking how far each component has moved into the super repo. The README defines three states. Completed means the component is fully migrated and the super repo is now the source of truth, though the old repo may still be used for some release activities. In Progress means migration, tests, or integration are ongoing, and the README asks contributors not to open new pull requests on the individual repo but to develop on the super repo instead. Pending means the work has not started or is in early planning, so the individual repo remains the source of truth. The examples given include composablekernel, hipblas, and hipblas-common, all listed as Completed in the snippet shown. The table also carries math CI status links for some components, pointing to the internal ROCm CI, so a reader can check whether a given library's precheckin tests are passing. This migration framing is important for contributors, because knowing the state tells you where to send a patch. A component marked Completed should be patched here, while a Pending one should still be patched in its old home. The README's honesty about state prevents wasted effort and makes the consolidation manageable over time.

Build and contribution notes

The README is oriented toward ROCm library developers rather than end users, so it does not read like an install guide for running models. Its purpose is to be the integration point where builds and tests run across components, and the CI badges are the main signal of health. The mention of TheRock as the build system tells a contributor that the familiar ROCm build flow now operates at the super repo level, and the nightly CI badge suggests continuous testing rather than only on demand runs. Because the migration is partial, the README's instruction to avoid new PRs on individual repos for In Progress components is the key rule to follow, and it reflects a careful cutover rather than a hard switch. The repository's primary language is listed as Assembly, which reflects the low level kernels present in the math libraries, though much of the tree is also build configuration and C or C++ source that the metadata does not surface as the top language. The license is not set to a standard SPDX identifier, so the precise terms live in the repository's own license files, and anyone redistributing built artifacts should consult those. For tracking ROCm's library development, this super repo is now the place to look as more components reach the Completed state.

Editorial conclusion

The repository declares no standard SPDX license and is primarily assembly and build configuration.