Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

ASM -> C ≠ C -> LLMs

34,368 görüntüleme • 15 gün önce •via X (Twitter)

17 Yorum

LaurieWired profil fotoğrafı
LaurieWired15 gün önce

same reason why the highest reliable language decompilers (ghidra, ida, etc) can reconstruct from arbitrary binaries is…pseudo-c. predictable enough that you can reverse it

Ryan Fleury profil fotoğrafı
Ryan Fleury15 gün önce

That is fascinating!

LaurieWired profil fotoğrafı
LaurieWired15 gün önce

honestly I recommend any dev to try reverse engineering their own (small) binaries at least once! try writing a really simple program in C, and then do it again in rust. drop it in ghidra, use a model / mcp / whatever to churn away at it, and watch how different (or not!) the decompilation is from the original source code. you'll be surprised how it looks...especially rust (lol)

MemoryLeak profil fotoğrafı
MemoryLeak15 gün önce

Content like this is why I open this piece of shit twitter thing.

_D profil fotoğrafı
_D15 gün önce

A major point of C was to create a layer of abstraction to enable portability across many architectures. If we lived in a monoarchitecture world where all hardware was identical, I'd imagine there would still be a hold out assembly programmers who hold quality above all else.

Jawaid Bazyar profil fotoğrafı
Jawaid Bazyar15 gün önce

The contract for C code to ASM is "the ASM will produce the same outputs for the same inputs". You can specify contracts of that type for LLM code.

Ryan Fleury profil fotoğrafı
Ryan Fleury15 gün önce

That is not the contract for C code to ASM. But in any case, if the contracts are not computable, then they cannot be trusted by themselves.

Mangy Bear (หมีขี้เรื้อน) profil fotoğrafı
Mangy Bear (หมีขี้เรื้อน)15 gün önce

I can’t believe we have to have this totally retarded discussion but here we are 🤦

binit profil fotoğrafı
binit15 gün önce

yeah the thing is LLMs are non deterministic while C compilers are supposed to be deterministic. I can exactly predict what it will output from a compiler but not the same from a LLM

Annu Singh profil fotoğrafı
Annu Singh15 gün önce

It takes intelligence to design and craft a flute. Once created, the instrument reliably produces a musical tone when played correctly. A compiler is like a flute (tool), and a program is like music.

manohhoerse profil fotoğrafı
manohhoerse15 gün önce

Very interesting video, probably. I'm sure the content is very deep. I just couldn't hear a word over how good that beard looks.

Damian Gray profil fotoğrafı
Damian Gray15 gün önce

Like all analogies, it breaks down the closer you get to the source.

Sadly life respecter profil fotoğrafı
Sadly life respecter15 gün önce

I mean if you ask an LLM , “solve XYZ” and it just solves XYZ, 99% of the tlime, even it can be super predictable. You just don’t like the fact that it solves XYZ, you would rather be doing that problem solving. Unfortunately the time of human problem solving is over

Ryan Fleury profil fotoğrafı
Ryan Fleury15 gün önce

Embarrassing response & instantly trivially disproven

verse  profil fotoğrafı
verse 15 gün önce

off topic but what camera are you using? looks reallly clean and detailed

The Coredump Whisperer profil fotoğrafı
The Coredump Whisperer15 gün önce

PDP-11 heritage that we take for granted today through Intel and other ISAs...is C maps best to ISAs that used a heavily stack based abstraction with native hw stack frames call graphs. Recursion, nested calls, local variables, and function pointers etc. came easier.

Gerson Sosa profil fotoğrafı
Gerson Sosa15 gün önce

You cut off right at the point it was getting interesting, the real question for me is: how can you make these tools as realiable as a compiler, these are supposedly stochastic

Benzer Videolar

>[ T A C T I C A L - F R ]
0:59

Sensitive content

>[ T A C T I C A L - F R ]

𝙊𝙥𝙧𝙚𝙠

37,185 görüntüleme • 1 yıl önce