# AMD Adds a CPU-Threading Route to GPUs in ROCm 10.1

Published 2026-10-06 · AI.info Team · AI.info

> AMD’s ROCm 10.1 release, published October 5, adds hipThreads to map standard C++ threading concepts onto AMD GPUs without a full HIP rewrite. The update also changes GPU data transfers, host-memory placement, compiler tooling and support for running ROCm inside WSL2.

AMD’s [ROCm](https://rocm.blogs.amd.com/ecosystems-and-partners/rocm-10.1-blog/README.html) 10.1 release adds a way to move some existing CPU-threaded C++ code onto its GPUs without rewriting an application around HIP, the company’s GPU programming platform. The new library, hipThreads, maps standard C++ threading concepts to GPU execution and is aimed at workloads where a full port would take more effort than the expected benefit. AMD published the release on October 5, 2026.

## hipThreads targets incremental ports

ROCm 10.1 places hipThreads in the ROCm Core SDK’s threading libraries. hipThreads brings standard C++ threading concepts into heterogeneous device programming and can run on Linux and Windows. Its stated target is parallel CPU code that developers want to accelerate without undertaking a complete migration to the HIP programming model.

The [hipThreads documentation](https://rocm.docs.amd.com/projects/hipThreads/en/docs-10.1.0/) describes the library as providing C++-style concurrency primitives that run inside GPU kernels. Existing `std::thread`-style CPU code can be ported with few source changes, the documentation says. That offers a narrower entry point for some codebases, but does not mean any threaded program can move to a GPU unchanged.

## Storage and memory take a larger role

AMD’s other headline changes address the movement of data to and around accelerators. ROCm 10.1 expands hipFile, part of AMD Infinity Storage, with an asynchronous path that runs reads and writes on a HIP stream without the usual host-memory staging step. The release also adds a batch I/O interface for submitting multiple file requests and telemetry intended to help developers identify whether compute, memory or data delivery is limiting a workload.

The HIP runtime now lets applications allocate host memory on a specified CPU NUMA node. That can keep memory closer to the processor or accelerator using it, rather than relying on a generic pool. Libraries such as RCCL can use the capability to build NUMA-local, zero-copy communication pipelines, AMD says.

## LLVM 24 brings a build-system change

ROCm 10.1 moves AMD’s compiler development from LLVM 23 to LLVM 24. The newer compiler brings updated C++ support, and caching link-time optimization partitions can let incremental builds reuse unchanged portions of HIP device code, AMD says. The company warns that developers upgrading from ROCm 10.0 should check scripts keyed to the compiler version: the `clang_major` macro now reports 24.

The update also revises libraries and tools. MIGraphX switches its backend compiler from rocMLIR to rocMLIRTriton; rocSPARSE adds triangular solves for matrices in ELLPACK format. Separately, ROCm’s kernel-replay profiler feature is in beta, while Windows Subsystem for Linux 2 support enters tech preview, allowing ROCm packages to run inside a Linux guest using the Windows host driver.

## Performance claims await workload-level evidence

ROCm 10.1’s new pieces address different costs in GPU development: converting threaded code, moving data from storage, placing host memory and rebuilding large projects. That breadth makes the release relevant beyond the new programming library, particularly for teams whose accelerators spend time waiting on data or whose code has not been ported to HIP.

AMD’s announcement does not publish performance measurements for hipThreads or quantify how much the new I/O path improves throughput. Developers will need to test whether their specific CPU-threaded workloads map well to GPU execution and whether the reduced staging and NUMA traffic matter for their systems.

## Sources

1. Original source · Blog post [ROCm Blogs](https://rocm.blogs.amd.com/ecosystems-and-partners/rocm-10.1-blog/README.html) rocm.blogs.amd.com

Other pages read

2. [AMD ROCm Documentation](https://rocm.docs.amd.com/projects/hipThreads/en/docs-10.1.0/) rocm.docs.amd.com

## Companies in this story

- [Silo AI](https://ai.info/companies/silo-ai)

## Related stories

- [AMD details GPU-initiated DMA transfers for multi-GPU workloads](https://ai.info/news/amd-gpu-initiated-dma-multi-gpu)
- [Cerebras puts split AI inference into production with AMD GPUs](https://ai.info/news/cerebras-disaggregated-inference-amd-production)
- [vLLM details opt-in FlyDSL MonoKernels for faster decode on AMD GPUs](https://ai.info/news/vllm-flydsl-monokernels-agent-inference)
- [AMD adds MI450X accelerator and reports MI455X inference results](https://ai.info/news/amd-mi450x-helios-mi455x-inference-results)
- [Unsloth Desktop adds local inference on AMD XDNA 2 NPUs in Ryzen AI PCs](https://ai.info/news/amd-unsloth-xdna-2-npu-agentic-ai-apps)

## Explore

[More articles](https://ai.info/news)

---

Canonical: https://ai.info/news/amd-rocm-10-1-hipthreads-cpu-code-gpus
