vllm - 💡(How to fix) Fix [ROCm]: Docker/CMake build support for gfx1103 (Radeon 780M / RDNA3 APU)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

A proposed patch for (1) — adding gfx1103 to HIP_SUPPORTED_ARCHS plus the corresponding Docker build wiring — was drafted in #31062 (closing in favor of this tracking issue, since I can't validate gfx1103 end-to-end on my current hardware). The diff there can serve as a starting point for anyone with gfx1103 access who wants to pick this up.

  • Affected files in the proposed patch: CMakeLists.txt, docker/Dockerfile.rocm_base.
  • Hardware: Radeon 780M / RDNA3 APUs (gfx1103).
RAW_BUFFERClick to expand / collapse

🚀 The feature, motivation and pitch

vLLM's ROCm Docker images (docker/Dockerfile.rocm_base) and the CMake build (CMakeLists.txtHIP_SUPPORTED_ARCHS) do not currently support gfx1103 (Radeon 780M and related RDNA3 APUs). Users on these integrated GPUs hit two distinct problems when trying to build/run vLLM in a container:

  1. CMake rejects the arch. gfx1103 is not listed in HIP_SUPPORTED_ARCHS, so the build fails early even when PYTORCH_ROCM_ARCH=gfx1103 is set.
  2. rocBLAS TensileLibrary.dat does not ship gfx1103 kernels in current ROCm releases — this is an upstream AMD limitation rather than a vLLM bug, but it affects the end-to-end experience and is worth documenting.

A proposed patch for (1) — adding gfx1103 to HIP_SUPPORTED_ARCHS plus the corresponding Docker build wiring — was drafted in #31062 (closing in favor of this tracking issue, since I can't validate gfx1103 end-to-end on my current hardware). The diff there can serve as a starting point for anyone with gfx1103 access who wants to pick this up.

Prior testing and reproduction details were contributed by @yurikhan in the #31062 thread.

Alternatives

  • Document gfx1103 as explicitly unsupported until rocBLAS ships kernels for it upstream.
  • Provide a build path that allows experimental/unsupported archs through with a clear warning.

Additional context

  • Affected files in the proposed patch: CMakeLists.txt, docker/Dockerfile.rocm_base.
  • Hardware: Radeon 780M / RDNA3 APUs (gfx1103).

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [ROCm]: Docker/CMake build support for gfx1103 (Radeon 780M / RDNA3 APU)