HIP (AMD ROCm)
Ranked 6 of 12 GPU compute frameworks by recommenders
Free, open-source toolkit from AMD for porting CUDA code to AMD GPUs, built on LLVM. Common caveat: weak debugging tools and older GPUs dropped from the support matrix.
Free, open-source toolkit from AMD for porting CUDA code to AMD GPUs, built on LLVM. Common caveat: weak debugging tools and older GPUs dropped from the support matrix.
21 people gave an opinion
- recommend it
- 12
- criticize it
- 9
- approval share
- 57%
Recommended in 8 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 12 people recommend itNeeds 10 or more, met.
- 1.3 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 8 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Open-source LLVM-based toolchain
“I'd far prefer us all focusing on open standards like HIP, SYCL, OpenCL”
Comment from 13 Sep 2026 in “CUDA for AMD on Windows” “HIP is better because it's an open-source llvm backend/frontend”
Comment from 19 Jul 2026 in “Neither GCC nor Clang are compliant with standard C++” Eases porting CUDA code
“HIP and ROCm have actually made amazing strides in making CUDA developers' porting work easy”
Comment from 1 Aug 2026 in “Attention Decode on AMD MI450 GPUs: A Gluon Kernel Optimization Guide” “HIP is very similar syntax to CUDA”
Comment from 4 Dec 2025 in “RAM is so expensive, Samsung won't even sell it to Samsung”
What people warn about
Each mark is one comment
Drops older GPUs from support
“AMD's biggest issue has been dropping its older GPU micro-architectures from the ROCm/HIP support matrix too soon”
Comment from 24 Jul 2026 in “AMD's Instinct MI455X: Aiming for the Sun” “Vega and Polaris GPUs were dropped from the ROCm/HIP support Matrix long before AMD stopped selling new GPUs and APUs”
Comment from 22 Jul 2026 in “Supporting ATI TeraScale GPUs from 2007-2009 in RPCS3” Not a drop-in CUDA replacement
“it's a porting kit, not a compatibility layer, so you can't run arbitrary CUDA apps on AMD GPUs”
Comment from 18 Feb 2026 in “BarraCUDA Open-source CUDA compiler targeting AMD GPUs” “All those are far from the 1:1 CUDA experience.”
Comment from 11 May 2026 in “CUDA-oxide: Nvidia's official Rust to CUDA compiler” “Is HIP a drop in replacement? No.”
Comment from 18 Feb 2026 in “BarraCUDA Open-source CUDA compiler targeting AMD GPUs”
Other GPU compute frameworks people recommend
The four most recommended other GPU compute frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| NVIDIA CUDA | 91 | 73 | 55% | 12 | 18 yrs3 owners | — |
| AMD ROCm | 47 | 97 | 33% | 11 | 3 yrs4 owners | — |
| BarraCUDA | 21 | 7 | 75% | 2 | — | — |
| Triton | 18 | 2 | 90% | 8 | — | Approved |
| HIP (AMD ROCm)This page | 12 | 9 | 57% | 8 | — | — |
What people said
22 of the 23 comments that mention it, newest first. Each links to the original comment.
“I'd far prefer us all focusing on open standards like HIP, SYCL, OpenCL”
“the only reason people put up with it is because Vulkan and HIP C/C++ are even worse”
“HIP and ROCm have actually made amazing strides in making CUDA developers' porting work easy”
“AMD's biggest issue has been dropping its older GPU micro-architectures from the ROCm/HIP support matrix too soon”
“Vega and Polaris GPUs were dropped from the ROCm/HIP support Matrix long before AMD stopped selling new GPUs and APUs”
“HIP is better because it's an open-source llvm backend/frontend”
“rocM and HIP still aren’t very popular especially for research.”
“HIP doesn't always win against RADV/ACO, but on dispatch/runtime, it does appear to be quite a bit faster than HIP/LLVM on gfx1151”
“Nothing on chain, no blockchains. Just DNS / SSL like decentralization.”
“HIP was hard-coded for one GPU architecture. CUDA did it right, it has a intermediate virtual assembly PTX”
“the actual support and debugging tools remain so atrocious that it doesn't help”
“It works for simple stuff but loses terribly for frontier kernels”
“All those are far from the 1:1 CUDA experience.”
“HIP is just one of many examples of how utterly incompetent AMD is at software development.”
“HIP has been dismissed for years because it was a token effort at best.”
“Is HIP a drop in replacement? No.”
“it's a porting kit, not a compatibility layer, so you can't run arbitrary CUDA apps on AMD GPUs”
“Nowadays it works pretty well on a few supported GPUs (CDNA 3 and RDNA 4).”
“HIP is very similar syntax to CUDA”
“Vulkan Compute is catching up with HIP (or whatever the compatibility stuff is called now)”
“With HIP in the GPGPU world I'm able to set breakpoints in a GPU kernel and step through line by line.”
“these frameworks are rather opinionated about kernel design, they seem suboptimal for implementing a language runtime”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.