ROCm is free, libre and open-source software (except the GPU firmware blobs[4]), and it is distributed under various licenses. ROCm initially stood for Radeon Open Compute platform; however, due to Open Compute being a registered trademark, ROCm is no longer an acronym — it is simply AMD's open-source stack designed for GPU compute.
Heterogeneous System Architecture Intermediate Language
HSAIL[7] was aimed at producing a middle-level, hardware-agnostic intermediate representation that could be JIT-compiled to the eventual hardware (GPU, FPGA...) using the appropriate finalizer. This approach was dropped for ROCm: now it builds only GPU code, using LLVM, and its AMDGPU backend that was upstreamed,[8] although there is still research on such enhanced modularity with LLVM MLIR.[9]
Programming abilities
This section needs expansion. You can help by adding to it. (January 2022)
ROCm as a stack ranges from the kernel driver to the end-user applications.
AMD has introductory videos about AMD GCN hardware,[10] and ROCm programming[11] via its learning portal.[12]
One of the best technical introductions about the stack and ROCm/HIP programming, remains, to date, to be found on Reddit.[13]
Hardware support
ROCm is primarily targeted at discrete professional GPUs,[14] but unofficial support includes the Vega family and RDNA 2 consumer GPUs.
Accelerated Processor Units (APU) are "enabled", but not officially supported. Having ROCm functional there is involved.[15]
As of version 3.0, Blender can now use HIP compute kernels for its renderer cycles.[27]
Other Languages
Julia
Julia has the AMDGPU.jl package,[28] which integrates with LLVM and selects components of the ROCm stack. Instead of compiling code through HIP, AMDGPU.jl uses Julia's compiler to generate LLVM IR directly, which is later consumed by LLVM to generate native device code. AMDGPU.jl uses ROCr's HSA implementation to upload native code onto the device and execute it, similar to how HIP loads its own generated device code.
AMDGPU.jl also supports integration with ROCm's rocBLAS (for BLAS), rocRAND (for random number generation), and rocFFT (for FFTs). Future integration with rocALUTION, rocSOLVER, MIOpen, and certain other ROCm libraries is planned.
Software distribution
Official
Installation instructions are provided for Linux and Windows in the official AMD ROCm documentation. ROCm software is currently spread across several public GitHub repositories. Within the main public meta-repository, there is an XML manifest for each official release: using git-repo, a version control tool built on top of Git, is the recommended way to synchronize with the stack locally.[29]
AMD starts distributing containerized applications for ROCm, notably scientific research applications gathered under AMD Infinity Hub.[30]
AMD distributes itself packages tailored to various Linux distributions.
This section needs expansion. You can help by adding to it. (January 2022)
There is one kernel-space component, ROCk, and the rest - there is roughly a hundred components in the stack - is made of user-space modules.
The unofficial typographic policy is to use: uppercase ROC lowercase following for low-level libraries, i.e. ROCt, and the contrary for user-facing libraries, i.e. rocBLAS.[35]
AMD is active developing with the LLVM community, but upstreaming is not instantaneous, and as of January 2022, is still lagging.[36] AMD still officially packages various LLVM forks[37][38][9] for parts that are not yet upstreamed – compiler optimizations destined to remain proprietary, debug support, OpenMP offloading, etc.
Support libraries implemented as LLVM bitcode. These provide various utilities and functions for math operations, atomics, queries for launch parameters, on-device kernel launch, etc.
ROCt – Thunk
The thunk is responsible for all the thinking and queuing that goes into the stack.
ROCr – Runtime
The ROC runtime is a set of APIs/libraries that allows the launch of compute kernels by host applications. It is AMD's implementation of the HSA runtime API.[39] It is different from the ROC Common Language Runtime.
The common language runtime is an indirection layer adapting calls to ROCr on Linux and PAL on windows.
It used to be able to route between different compilers, like the HSAIL-compiler. It is now being absorbed by the upper indirection layers (HIP and OpenCL).
ROCm ships its installable client driver (ICD) loader and an OpenCL[40]implementation bundled together.
As of January 2022, ROCm 4.5.2 ships OpenCL 2.2, and is lagging behind competition.[41]
The AMD implementation for its GPUs is called HIPAMD. There is also a CPU implementation mostly for demonstration purposes.
HIPCC
HIP builds a `HIPCC` compiler that either wraps Clang and compiles with LLVM open AMDGPU backend, or redirects to the NVIDIA compiler.[42]
HIPIFY
HIPIFY is a source-to-source compiling tool. It translates CUDA to HIP and reverse, either using a Clang-based tool, or a sed-like Perl script.
GPUFORT
Like HIPIFY, GPUFORT is a tool compiling source code into other third-generation-language sources, allowing users to migrate from CUDA Fortran to HIP Fortran. It is also in the repertoire of research projects, even more so.[43]
High-level
ROCm high-level libraries are usually consumed directly by application software, such as machine learning frameworks. Most of the following libraries are in the General Matrix Multiply (GEMM) category, which GPU architecture excels at.
The majority of these user-facing libraries comes in dual-form: hip for the indirection layer that can route to Nvidia hardware, and roc for the AMD implementation.[44]
Nvidia's CUDA is closed-source, whereas AMD ROCm is open source. There is open-source software built on top of the closed-source CUDA, for instance RAPIDS.
CUDA is able run on consumer GPUs, whereas ROCm support is mostly offered for professional hardware such as AMD Instinct and AMD Radeon Pro.
Like ROCm, oneAPI is open source, and all the corresponding libraries are published on its GitHub Page.
Unified Acceleration Foundation (UXL)
Unified Acceleration Foundation (UXL) is a new technology consortium that are working on the contiuation of the OneAPI initiative, with the goal to create a new open standard accelerator software ecosystem, related open standards and specification projects through Working Groups and Special Interest Groups (SIGs). The goal will compete with Nvidia's CUDA. The main companies behind it are Intel, Google, Arm, Qualcomm, Samsung, Imagination, and VMware.[45]
See also
AMD Software – a general overview of AMD's drivers, APIs, and development endeavors.
![[icon]](File:Wiki_letter_w_cropped.svg){kind=small}
