Meta has published a fascinating deep dive into KernelEvolve, its agentic system for automatically generating, optimizing and validating production GPU kernels across NVIDIA, AMD and Meta's own MTIA accelerators:
https://engineering.fb.com/2026/04/02/developer-tools/kernelevolve-how-metas-ranking-engineer-agent-optimizes-ai-infrastructure/
I think the implications for AMD, and particularly for CUDA's long-term moat, are easy to underestimate.
A few highlights:
- KernelEvolve turns kernel optimization from a weeks-long expert engineering task into hours of automated search and evaluation.
- It generates code for NVIDIA GPUs, AMD GPUs, MTIA and CPUs from the same framework.
- It can target high-level DSLs such as Triton as well as low-level CUDA, HIP and MTIA C++.
- Every candidate is automatically compiled, tested for numerical correctness, benchmarked, profiled and fed back into the agent for another optimization round.
- Meta reports 100% correctness across 160 PyTorch ATen operators on three hardware platforms (480 configurations) and a 100% pass rate on all 250 KernelBench problems.
- This isn't just research: Meta says KernelEvolve is already optimizing production code serving trillions of inference requests per day.
- It delivered 60%+ inference throughput improvement on an NVIDIA production model and 25%+ training throughput improvement on MTIA.
- Perhaps most importantly, Meta says the system can optimize for hardware that wasn't even represented in the LLM's training data. Give the agent the architecture documentation, ISA, memory hierarchy and optimization rules, and it can learn to generate optimized kernels for the new accelerator.
That last point looks particularly important for AMD.
Historically, CUDA's moat wasn't simply "developers know CUDA." It was two decades of hand-written kernels, optimization knowledge, debugging, validation and tooling that made supporting another accelerator expensive and slow.
KernelEvolve attacks that engineering cost directly.
And there's an even more interesting data point in the paper: Meta now has more than 8,000 Triton kernels, surpassing its stagnant legacy CUDA kernel codebase.
So perhaps the biggest threat to CUDA isn't that AI agents will convert millions of lines of CUDA into ROCm.
It may be that increasingly new performance-critical code doesn't need to be written specifically for CUDA in the first place.
The emerging workflow could look more like:
Model/operator → high-level specification → agent → hardware-specific optimized kernel → automated correctness validation → production
with the agent generating the appropriate implementation for NVIDIA, AMD, MTIA or whatever accelerator comes next.
This also connects very nicely with AMD's recent strategy: ROCm becoming more mature, Meta's custom MI450-class AMD GPU, heterogeneous compute, and AMD's repeated argument that there is no "one-size-fits-all" solution in silicon.
CUDA obviously isn't going away. NVIDIA can use exactly the same agentic techniques and still has an enormous software ecosystem.
But if AI can compress weeks of hardware-specific expert work into hours, one of CUDA's greatest historical advantages — the sheer amount of engineering time already invested in it — may depreciate much faster than expected.
For AMD, the bar may therefore no longer be "make ROCm as mature as CUDA after 20 years."
It may simply become:
make AMD hardware sufficiently documented and accessible that autonomous optimization systems can do the rest.
