HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ROCm
legacy-rocm-build
Shell2016–2026
ROCm / legacy-rocm-build · Archived

legacy-rocm-build

AMD ROCm™ Software - GitHub Home

Learning & Reference
Explore on GitHubRead Hacker News discussions
92Distinct people
119Mentions
0Explicit recommenders
6.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

AMD ROCm™ Software - GitHub Home

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year119 dated mentions

Observed mentions: 2016-04-27 13:48:21 UTC to 2026-08-12 14:18:54 UTC.

01020302016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 15 mentions; 1 submissions, 14 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 18 mentions; 0 submissions, 18 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 31 mentions; 2 submissions, 29 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 4 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC312
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC606
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC422
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC927
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC15114
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC18018
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC31229
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC15312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC945
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
WarningThis repository will be deprecated soon. Use ROCm/TheRock moving forward, including for issues and discussions. Open-source software stack for AMD GPU computing ROCm Core SDK • AI Ecosystem • GPU Systems and Infrastructure • Blogs AMD ROCm™ ROCm is an open-source software stack of drivers, development tools, and APIs that enable GPU programming from low-level kernels to end-user applications. It is particularly well-suited to GPU-accelerated high-performance computing (HPC), AI, scientific computing, and computer-aided design (CAD). ROCm is powered by HIP, a C++ runtime API and kernel language that lets developers write portable GPU code with an interface similar to NVIDIA CUDA™. It also supports OpenMP and OpenCL, and includes the compilers, debuggers, and libraries needed to build and run GPU workloads. ROCm integrates with machine learning frameworks such as PyTorch and TensorFlow. Table of contents Supported hardware and operating systems Quick start Get started with ROCm Deep learning frameworks on ROCm Core components Math and compute libraries Communication libraries Runtimes and compilers Profiling and debugging tools Control and monitoring tools Media libraries Storage ROCm Extras Release notes Licenses Contribute Supported hardware and operating systems Use the Compatibility matrix for official support across ROCm versions, operating system kernels, and GPU architectures (CDNA/Instinct™, RDNA/Radeon™, and Radeon Pro). Recent releases cover Ubuntu, RHEL, SLES, Oracle Linux, Debian, Rocky Linux, and more. GPU targets include CDNA4, CDNA3, CDNA2, RDNA4, and RDNA3. Quick start Follow these instructions to start using ROCm. Get started with ROCm Follow the ROCm installation guide to install ROCm on your system. Deep learning frameworks on ROCm See Install PyTorch for ROCm or Install JAX for ROCm to get started. To learn more about AI training and inference workloads on ROCm, see the AI Ecosystem documentation portal. Core components The core ROCm software stack consists of the following components. Most of them are divided across the ROCm Libraries and ROCm Systems super-repos by domain. Math and compute libraries Composable Kernel hipBLAS and rocBLAS hipBLASLt hipCUB hipFFT and rocFFT hipRAND and rocRAND hipSOLVER and rocSOLVER hipSPARSE and rocSPARSE MIOpen rocPRIM rocThrust rocWMMA Communication libraries RCCL rocSHMEM Runtimes and compilers HIP HIPIFY LLVM ROCr Runtime SPIRV-LLVM-Translator Profiling and debugging tools ROCm Compute Profiler (rocprofiler-compute) ROCm Systems Profiler (rocprofiler-systems) ROCprofiler-SDK ROCdbgapi ROCgdb ROCR Debug Agent Control and monitoring tools AMD SMI ROCm Data Center Tool rocminfo Media libraries rocDecode rocJPEG Storage hipFile For a complete list of foundational ROCm components, see ROCm Core SDK components. ROCm Extras ROCm Extras include supplementary tools for benchmarking, validating, and managing ROCm deployment. ROCm Validation Suite (RVS) TransferBench ROCm Optiq Release notes Latest ROCm release For information on older ROCm releases, see the ROCm release history. Licenses ROCm licenses Contribute AMD welcomes ROCm contributions using GitHub PRs or issues. See the links below for contribution guidelines. ROCm TheRock ROCm documentation ROCm Systems ROCm Libraries
Read the full README on GitHub

What Hacker News says

119 sources
lhl·Aug 12, 2026
For updated/validated updates, Donato Capitella maintains independent Strix Halo "toolboxes": https://strix-halo-toolboxes.com/ A team from AMD maintains Lemonade, another all-in-one setp with convenient installers for setting everything up: https://lemonade-server.ai/ These are probably better than running against llama.cpp ROCm directly as there are frequent/constant regressions on the main branch, especially for gfx1151 (Strix Halo), but RDNA in general. There are number of AMD-focused llama.cpp forks (nathanw1014, charlie12345, ciru-ai, justinappler, etc) - as well as a few alternatives like hipfire or my hipEngine. While ROCm has gotten a lot better, one of the things I've found after writing an inference engine that has completely custom tuned/fused C++/HIP kernels, is that while it's been pretty straightforward to match/beat llama.
Read the rest
cpp ROCm performance, that Vulkan RADV has been a lot harder since RDNA3 support for ROCm has a few issues that make it underperform ACO on some common operations on both gfx1100 and gfx1151 (see: https://github.com/ROCm/ROCm/issues/6409 ) In general, for anyone just looking to run LLM models on an AMD card, I'd just recommend going with llama.cpp Vulkan and skipping ROCm completely.
In llama.cpp
jauntywundrkind·Jul 28, 2026
I mean, Nvidia says CUDA Tiles says CUDA Tiles MLIR is open source. https://news.ycombinator.com/item?id=46330732 Afaik, AMD, Google, and everyone else is still using some combo of mostly XLA, with StableHLO, IREE, etc? https://openxla.org/ I was going to lightly blow off more steam about AMD's TheRock all-in-one monorepo-ish thing for their graphics drivers being basically unbuildable on anything but a single distro, with little attention to tickets, but (in spite of this ticket being open) it looks like AMD did file and close quite a lot of sub tickets that resolve a huge amount of the issues. Very good to see this transition; I was really concerned that this was all a show release for very certain partners but not serious, but this looks like they are being pretty go-for-it. https://github.com/ROCm/TheRock/issues/3477 It is a little al
Read the rest
arming to watch AMD try to move. On the one hand I think Senior Leadership did a very good very nice job setting forth some pretty solid hopeful goals. For day 0 Helios. They wrote it down, on github, which is such a hopeful good important differentiator, that I love. But, like, did their devs have good access to hardware, in quantity, to test and work on here? Why are these tickets so relatively quiet? Incredible ticket. Would that we could rely on anyone else in the world to do this. This is amazing. Of course, it's not done at all, and that looks bad, and I'm so scared to share it, in that light, but I just want to applaud so much, and suggest that this is how you break the moats. You open and share and talk. Also, like, get the work done. Get it working. But the range of tasks here is great too. AMD clearly sees what it takes. The IO acceleration stuff gives me confidence they understand the scope of the work, and that it's not just trying to slam a lot of gpu cores onto huge motherboards. https://github.com/ROCm/ROCm/issues/6335
In Can AMD Break the CUDA Moat? AMD Advancing AI 2026
theoli·Apr 23, 2026
There was this ROCm bug I was watching for awhile: https://github.com/ROCm/ROCm/issues/5706 - This is about the GPU clock remaining at max frequency, but that can drive the fan speed to increase. It doesn't happen with Vulkan backends, so that is what I have been using for my two dual R9700 hosts. EDIT: The bug is closed but there were mentions of the issue still occurring after closure, so who knows if it is really fixed yet.
In Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
thrtythreeforty·Apr 1, 2025
This ticket, finally closed after being open for 2 years, is a pretty good micocosm of this problem: https://github.com/ROCm/ROCm/issues/1714 Users complaining that the docs don't even specify which cards work. But it goes deeper - a valid complaint is that "this only supports one or two consumer cards!" A common rebuttal is that it works fine on lots of AMD cards if you set some environment flag to force the GPU architecture selection. The fact that this is so close to working on a wide variety of hardware, and yet doesn't, is exactly the vibe you get with the whole ecosystem.
In Ask HN: Why hasn’t AMD made a viable CUDA alternative?
FeepingCreature·Dec 4, 2024
Geohot (temporarily) giving up. https://github.com/ROCm/ROCm/issues/2198#issuecomment-157438... Sadly most of the real spicy Twitter messages are gone since he deleted all his content, but there was a really fun one where he went off on a beautifully cryptic commit message in the driver. He also begged AMD to opensource the firmware so he could debug it. Sadly, AMD promised to do it and then nothing happened, as is typical for AMD promises. That's why tinygrad nowadays is aiming to just bypass the driver and firmware entirely.
In Intel announces Arc B-series "Battlemage" discrete graphics with Linux support

Showing the 15 most recent of 119 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.