logoalt Hacker News

Frostbite: A new CPU architecture discovered, designed and verified by AI

564 points • by shioyama • today at 10:01 AM • 298 comments • view on HN

Comments

globalnode • today at 11:12 AM

hardware slopocalypse inc

ezrec • today at 2:28 PM

So... no one at Architect Labs ever played Zachtronics' "TIS-100"? Really?

jbrooks84 • today at 12:31 PM

Oh thank God AI verified it

lpapez • today at 1:34 PM

Babe wake up, CPU-slop has arrived.

badgersnake • today at 10:23 AM

Naming is hard I guess.

➕ show 2 replies
artemonster • today at 12:01 PM

(dual-issue, in-order) CPU core - this puts you in microcontroller core class and energy is the most important part here. at the end you see the numbers, but synthetic benchmarks have close to zero relevance in that scenario. all around fishy whitepaper-like ai slop corpo blogging to generate buzz

raverbashing • today at 11:14 AM

Discovered? I don't think this means what you think it means

It's not like Intel dug x86 from some mine in Oregon

FrustratedMonky • today at 10:53 AM

So far this thread is a little breathless about AI.

This looks cool and all.

But, can someone with CPU experience give an opinion? Does this blow your mind? Or is it trash?

Like how the new math solutions when read by a mathematician seem 'ugly', even if technically correct. Does this look like something actually alien and groundbreaking?

➕ show 2 replies
SecretDreams • today at 12:52 PM

Now they AI can sulk and dwell, wondering why adoption for their new architecture is low, like other, prior, new architectures after arm!

shevy-java • today at 12:38 PM

Ok but ...

... WHY ARE THE PRICES SO DAMN HIGH COMPARED TO THREE YEARS AGO?

rvz • today at 10:36 AM

Once again, you are "not allowed" to invest in the frontier.

imtringued • today at 10:53 AM

Looks like AI doesn't have to fall for C hubris. Honestly, if you want to make it in this new AI age I recommend you to question every single thing that is considered set in stone, anything that is considered "the natural order of things" in software development. Think hard outside the box.

I don't know why nobody is seeing the problems with C. From my perspective it's not useful to think of C as a portable assembler or a thin layer on "top of the machine", because it makes C machines look eternal and timeless, even though we are deep into the post C machine era of multi core processors with cache coherence.

>Mainstream programming languages, when compiled for general-purpose CPUs, hide the dependencies between the parts of a program. Any piece of code may read or write any variable through a shared, mutable state, and so modern CPU hardware assumes the worst case and rediscovers, at runtime, which instructions actually depend on each other.

To this day I still wonder why people aren't seeing the immediate glaring red flag that the conventional sequential programming model presents. To this day people keep building inherently sequential languages and then wonder why parallelism is so hard. It's hard because you made a fatal assumption: There is only one global memory. How exactly is anyone supposed to reason about such an omnipotent and all powerful concept, where everything can potentially affect anything? If you have two cores, the entire idea of a singular memory screams like a bottleneck. Like, it's crazy to me that anyone would think in 2026 "yup, lets build another sequential language that makes our lives a living hell".

>Moreover, single-core CPU performance has largely stalled since the early 2000s, pushing people towards large multicore CPUs such as Intel Xeon, AMD Zen, and NVIDIA Vera. This forces CPUs to maintain the illusion that every core sees the same memory, and keeping that illusion consistent and performant requires deep cache hierarchies and coherence protocols that cost area and power, and scale poorly.

Correct. Because everything potentially depends on everything, you need to figure out at runtime when things don't depend on each other, which is kind of insane when you think about it.

The assumption of a single global memory is what doomed C. It's the 21th century. Computers don't have global memories anymore, they pretend they do. You can't fix it. No amount of nostalgia towards C is going to fix this mistake.

Also before someone accuses me of e.g. being a C hater, I'll tell you that Zig's IO Backend parameters are the same type of flaw in Rust that probably will never be fixed. Implicit IO is a different kind of global state that Rust inherited and from the 2026 agentic coding perspective it's a pretty egregious flaw because agents don't care about passing in a parameter, meanwhile from the perspective of PL design, using a parameter instead of a full on effects system has this certain charm / beauty to it, how you don't need to special case everything to get the same results. You just use what is already there.

➕ show 6 replies
Vivek-KY • today at 10:28 AM

[dead]

chahmed312 • today at 11:22 AM

[flagged]

stpedgwdgfhgdd • today at 12:06 PM

[flagged]

encyclopediai • today at 2:25 PM

[dead]

ElUncivio • today at 11:32 AM

[dead]

ravivarmat • today at 12:31 PM

[dead]

olivedot • today at 3:56 PM

[flagged]

throwtis100 • today at 11:59 AM

[dead]

s08148692 • today at 10:39 AM

The future is going to be fascinating

If we have enough fabs theres a world where every single problem has a completely custom chip to maximise efficiency of whatever problem needs to be solved. End to end AI - Ask to solve a problem, AI designs the chips, fab delivers it, AI writes the software in a completely custom language. Nobody will understand how anything works other than knowing that it does work

➕ show 11 replies
atomsandbits • today at 10:54 AM

Future = AI + Robots