Live data from Hacker News

Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

github.com

71–80 of 88 posts

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#71
post #32

I just wish everyone read Summa Technologiae from Stanislaw Lem. This was obviously covered back in 1964, with the relevant implications. https://publicityreform.github.io/findbyimage/readings/lem.p...

Whats your take on it? "If I read it, what point should I pay attention to?", I guess is what I'm trying to say

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#72
post #2

Salient on the value of the verifier. Matches my experience in the last two quarters. Nice detail on the encountered failures. Very similar experiences with my own loops against testsuites. Great post. A snapshot in time.

Tks! Did you apply it to hardware design or to another field?

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#73
post #17

> The frontier is the verifier. Um, yes? The big value that AMD had in the x86 market over competitors was their verification model. This has been known for decades. > 3-seed nextpnr P&R on a Gowin GW2A-LV18 (Tang Nano 20K) — median Fmax × CoreMark iter/cycle = fitness Every single "improvement" is basically about routing around how absolutely abysmally bad the Gowin FPGAs are. Kudos to that, I guess? Gowin FPGAs hav…

Assuming that your claims about GoWin FPGA flaws are correct, isn’t the point of this experiment that it was able to exploit these flaws without manual guidance?

His claims are indeed correct; Yes, you got my point tks!; AND the loop produced architecture gains that are not exclusive to the GoWin FPGA (CoreMark/Mhz is higher than VexRiscV)

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#74
post #3

In case you are unfamiliar with Karpathy's Loop[1], it is a genetic algorithm[2] where the genetic "mutations" are clever-but-random ideas generated by an LLM agent, aimed at improving a system. (1) Let the LLM randomly perturbate the system. (2) Measure the system's performance. (3a) If the perturbation improved performance, keep the change. (3b) Otherwise, don't. (4) Repeat [1] https://github.com/karpathy/autoresea…

Lol, I respect karpathy a lot, but this is such an obvious in your face idea that it is laughable to put someone’s name on it. What’s next “karpathy investing” where ai in a loop builds a portfolio?

[dead]

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#75
post #3

In case you are unfamiliar with Karpathy's Loop[1], it is a genetic algorithm[2] where the genetic "mutations" are clever-but-random ideas generated by an LLM agent, aimed at improving a system. (1) Let the LLM randomly perturbate the system. (2) Measure the system's performance. (3a) If the perturbation improved performance, keep the change. (3b) Otherwise, don't. (4) Repeat [1] https://github.com/karpathy/autoresea…

Lol, I respect karpathy a lot, but this is such an obvious in your face idea that it is laughable to put someone’s name on it. What’s next “karpathy investing” where ai in a loop builds a portfolio?

Call it a K-loop please. Where ai in a k-loop builds a portfolio

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#76
post #3

In case you are unfamiliar with Karpathy's Loop[1], it is a genetic algorithm[2] where the genetic "mutations" are clever-but-random ideas generated by an LLM agent, aimed at improving a system. (1) Let the LLM randomly perturbate the system. (2) Measure the system's performance. (3a) If the perturbation improved performance, keep the change. (3b) Otherwise, don't. (4) Repeat [1] https://github.com/karpathy/autoresea…

Lol, I respect karpathy a lot, but this is such an obvious in your face idea that it is laughable to put someone’s name on it. What’s next “karpathy investing” where ai in a loop builds a portfolio?

I believe Karpathy himself called it autoresearch, not Karpathy Loop, but in a vacuum of names around AI it seems to be very easy to meme-drop a name and then come influencer efforts to cool-name and normalize it. See vibecoding*

Re: Show HN: Auto-Architecture: Karpathy's Loop, pointed at a CPU

#80

Earlier quoted context omitted.

Lol, I respect karpathy a lot, but this is such an obvious in your face idea that it is laughable to put someone’s name on it. What’s next “karpathy investing” where ai in a loop builds a portfolio?

I'd go a step further and say that sort of loop is probably the first thing most people who play around with agent harnesses try, pretty much the first "Hmm, what should I do now?" thing that pops into people's head.

actually having a harness for it is nice though, vs having yourself prompt it interatively.
Post reply on HN