Hourly ·
Google reportedly taps AMD to design its next-generation TPU
SemiAnalysis reports Google is working with AMD on a 10th-generation TPU that could pair its tensor cores with on-package CPU cores — AMD's first foray into custom AI silicon, aimed at reinforcement-learning workloads.
Google is reportedly bringing in AMD to help design one of its upcoming 10th-generation TPUs, according to a SemiAnalysis research note cited by Tom's Hardware. If accurate, the move would mark AMD's first real involvement in a custom AI ASIC — a notable shift after nine TPU generations in which Broadcom served as Google's de facto silicon design partner.
The more interesting question is why Google would need AMD at all. Google already builds its own accelerator architecture, so SemiAnalysis analysts think the draw is AMD's CPU cores rather than its accelerator know-how. Google and its cloud customers are pushing for TPUs that place general-purpose CPU cores on the same package as the tensor cores, tuned for reinforcement-learning and agentic workloads — which demand far more surrounding general-purpose compute than conventional LLM training.
A hypothetical design could combine Google's TPU compute chiplets with AMD CPU and HBM in a single tightly integrated package, echoing AMD's Instinct MI300A data-center APU. Firstpost frames the report as a shift in Google's TPU strategy. For now the report remains speculative — but if it holds, the real story isn't another TPU. It's Google quietly betting on a CPU-heavy member of its chip family for the agentic era.
据报道,谷歌 reportedly 拨顾 英特尔 到设计其下一代 TPU
半分析报道谷歌与AMD合作开发一款第十代TPU,该芯片可能将Google的张量核心与AMD[3D[K AMD封装中的CPU核心搭配——这是AMD首次涉足定制AI硅片,旨在针对强化学习工作负载[K 。
← 日更新 Hourly · 2026-08-16 19:00 UTC 据报道,Google 正与 AMD 合作设计其下[K 一代 TPU。这些分析称 Google 将与 AMD 协同设计一个带有定制张量核心的第 10 代[K TPU,这将是 AMD 在自定义 AI 芯片领域的首次尝试,目标是针对强化学习负载的工[K 作负载。Google 据报道正邀请 AMD 帮助设计其即将推出的一个 TPU。
More Hourlies Stories
Content on Anagnorisis is summarized, paraphrased, and editorialized from publicly available sources for length and clarity. Original sources are linked where available. All trademarks belong to their respective owners.
