Next PlayStation and Xbox Consoles Are Rumored to Feature AMD UDNA/RNDA 5 Graphics

shared L1 cache eliminates data replication across GPU cores, improving collective hit rate & efficiency at the cost of increased latency for certain workloads (addressed by workgraphs & others), & die area.

Basically, net improvement in peak throughput.



in short a GPU with die size that is extremely competitive because of reduced L2 cache & removal of infinity cache.

in other words, ideal for consoles. this thing is built for consoles
 
It will be interesting to see what actually makes it to a card for us DIY folks and if it will only be offered in SOC situations.

I mean honest engine here.... if I can get a SOC system, with 64 or 128 gig of fast ram that can perform better than my tower sitting next to my monitor... and be a smaller form factor... I'd think long and hard about doing it.


EDIT: Problem being is that just becomes a more expensive console. You're commoditizing the entire experience, Not much different than a laptop you upgrade every 3-5 years.

DIY is supposed to be for those people that want to build your own without compromise, or with SPECIFIC compromise you want in order to achieve a goal within your budget window. Going to AIO units or SOC based systems means you leave all of that out and get what you buy and be happy with it damnit.

If I were a younger man and PC enthusiast the system in a box SOC based solutions would SUUUUUCK so hard because i couldn't build something to be what I want it to be, knowing I can swap pieces and parts as things change.
 
It will be interesting to see what actually makes it to a card for us DIY folks and if it will only be offered in SOC situations.

I mean honest engine here.... if I can get a SOC system, with 64 or 128 gig of fast ram that can perform better than my tower sitting next to my monitor... and be a smaller form factor... I'd think long and hard about doing it.


EDIT: Problem being is that just becomes a more expensive console. You're commoditizing the entire experience, Not much different than a laptop you upgrade every 3-5 years.

DIY is supposed to be for those people that want to build your own without compromise, or with SPECIFIC compromise you want in order to achieve a goal within your budget window. Going to AIO units or SOC based systems means you leave all of that out and get what you buy and be happy with it damnit.

If I were a younger man and PC enthusiast the system in a box SOC based solutions would SUUUUUCK so hard because i couldn't build something to be what I want it to be, knowing I can swap pieces and parts as things change.
think of a steam machine but instead of a separate mobile 7600m the igpu itself can do the job. then you can use unified ram. maybe 64gb or 128gb lpddr5x

ram would be costly for sure. but rest of the setup would cost same as steam machine

if you are willing to splurge $2000 to $4000 then you can go for the halo setup with double the igpu chiplet but bonkers unified RAM (mostly for offline/edge AI inferencing — will not be value for money for gamers)
 
you know there are several NUCs with high end CPUs and discrete video cards. They are expensive of course.
 
initial place holder for GFX13 aka RDNA 5. Very intriguing as there were earlier rumours that hardware will only be out in 2027 due to the AI bubble/ memory shortage situation



AMD GFX13 gfx1310 target appears in LLVM, hinting RDNA 5 development

Published 2 hours ago by Hilbert Hagedoorn

An AMD “GFX13” identifier has resurfaced in open-source tooling after a long period of little to no public movement, and this time it shows up where GPU enablement often begins: the LLVM compiler stack. Late on Friday, January 23, a public LLVM Project update was highlighted by Kepler_L2, revealing that initial support has been defined for an AMD “gfx1310” target. While the change is small on the surface, new “gfx” IDs are typically the first visible signs that a future architecture is being prepared across the software pipeline. A developer note attached to the update suggests gfx1310 is currently handled as a placeholder, treated as equivalent to RDNA 4-era identifiers, specifically GFX12 and GFX1250. That kind of temporary mapping is common when a new target is introduced: compiler infrastructure needs a recognized target name and basic plumbing before it can meaningfully express architectural differences. In practical terms, it means the target exists in the tree, but it is not yet differentiated in a way that reveals new instruction behavior, scheduling changes, or feature flags.

Even so, the return of “GFX13” is notable because it echoes older references from prior development notes. Before 2026, various patch notes and ecosystem discussions mentioned early “GFX13” work in the same orbit as next-generation AMD graphics architecture naming, including “RDNA 5” and “UDNA.”

The new LLVM entry does not confirm what AMD will ultimately call the architecture, and it certainly doesn’t confirm retail product branding. However, it does reinforce the idea that a post-RDNA 4 GPU target family is being staged on the compiler side. Some observers have pointed at LLVM 23-related activity and suggested the work is already tied to RDNA 5 specifically. At this stage, that’s still interpretation rather than confirmation: the “identical to GFX12/GFX1250” note implies gfx1310 is not yet exposing meaningful differences. The more grounded takeaway is that the target has been introduced early, and follow-up commits will be the ones that matter for understanding what gfx1310 actually represents.

As always, speculation quickly drifts toward product naming and timelines, including talk of a theoretical “Radeon RX 10000” desktop GPU family and a vague mid-2027 timeframe. Those ideas may align with typical generational pacing and even potential next console cycles, but none of that is established by a single compiler-target entry.


What the LLVM change does indicate is that the software groundwork has started—or restarted—in public view.


The next checkpoint will be further LLVM development. Phoronix founder Michael Larabel has already flagged interest in the LLVM 23.1 stable release expected around August/September, since that window could bring more commits that move gfx1310 from placeholder status toward real target definition. Until then, gfx1310 is best treated as an early breadcrumb: relevant, but not yet a roadmap in plain sight.


Source: LLVM Project, Kepler_L2, Phoronix, Wccftech, LLVM GitHub
 
Become a Patron!
Back
Top