On March 22nd, a LocalLLaMA user posted about running llama.cpp build b8464 on what appears to be AMD's Radeon RX 9700 — the mid-range RDNA 4 card that the local inference crowd has been watching with quiet intensity. The post is sparse in the way that genuinely interesting posts often are: no benchmarks attached, no tokens-per-second to fight about in the comments, no methodology to pick apart. The implied message is blunt and minimal. The card runs llama.cpp. Build b8464, specifically. It ran well enough that someone decided the internet needed to know. That is the full extent of what we have, and it has not moved since March 22nd.
If confirmed, here is what this means. The RX 9700 sitting comfortably inside llama.cpp's support window would matter considerably to the segment of the local inference community that cannot justify the cost of an RX 9900 XTX but refuses to accept the memory bandwidth ceiling of consumer Nvidia alternatives. RDNA 4's architectural improvements to compute density and memory efficiency were designed precisely for workloads that look like large language model inference — tight memory access patterns, sustained throughput, minimal idle cycles. A mid-range card from that generation clearing compatibility testing would effectively lower the price floor for serious local inference by several hundred dollars. It would also intensify the pressure on Nvidia's mid-range positioning at a moment when AMD can least afford to be ignored and Nvidia can least afford to be caught flat-footed.
Watch for independent benchmark posts on LocalLLaMA or Hugging Face forums citing the RX 9700 alongside actual token throughput figures, and for llama.cpp's issue tracker to surface any RDNA 4-specific fixes that would date when this support solidified.
<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1t4uj9h/mtp_on_strix_halo_with_llamacpp_pr_22673/"> <img alt="MTP on strix halo with llama.cpp (PR #22673)"
<!-- SC_OFF --><div class="md"><p>So i recently updated LMstudio after a long pause and updated my llama.cpp runtimes too.. i was shocked.. i thought maybe something like
<!-- SC_OFF --><div class="md"><p>That foodtruck bench post showing deepseek v4 matching gpt-5.2 at 17x cheaper got me thinking. if frontier cloud models are that overpriced for
<!-- SC_OFF --><div class="md"><p>Got Qwen 3.5 27B to 1,103,941 tok/s on 12 nodes with 96 B200 GPUs.</p> <p>At that rate you process 50,000 insurance policy documents in hours
<!-- SC_OFF --><div class="md"><p>DeepSeek dropped the full V4 paper this week. preview from april was 58 pages, this version adds a lot of technical depth.</p> <p>What stood out
<!-- SC_OFF --><div class="md"><p>Every output token the model generates requires reading the entire KV cache from High Bandwidth Memory.</p> <p>Here's what that actually looks
<!-- SC_OFF --><div class="md"><p>Hey everyone, I've been working on getting Multi-Token Prediction (MTP) working with quantized GGUFs for Qwen3-27B and the results are pretty
<!-- SC_OFF --><div class="md"><blockquote> <p><strong>WARNING: wait before download from HF: I just realised my upload of the new versions with the additional fix in the chat
NewsHive monitors these sources continuously. All signal titles above link to the original reporting.
Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →