logoalt Hacker News

Kuna: Decompiler Development in the Age of Coding Agents

50 pointsby matt_dtoday at 2:41 AM10 commentsview on HN

Comments

gopalrajatoday at 9:45 AM

Yeah — i agree based on my own experience. It was that the loop only works because if you have a rubruc to measure againt. I’ve had similar issues but not in any decompiler mode. Agents can be deceptive in explaining something so well (and I was too lazy to carefully read it verify it myself). Where I got burned was when a beta tester pointed out some citations that didnt exist. So i put a check in place. agent can propose freely, unconfirmed stuff fails closed, my rubric checks get the veto. Same shape as what you’re describing. The agent can refine; the rubric metrics is what keeps it from just becoming fluent drift. Without that human in the loop, autonomous improvement is mostly relies on luck. On the other hand, I am seeing more and more the newer model's reasoning and having another llm eval (provided that llm has rubrics to measure against) does lessen the falseness.

saidnooneevertoday at 6:33 AM

this is really amazing work thank you and in my opinion (as its explained) a very good example of how to use AI powered development and research to advance the tools we have. decompilation is really hard, and better algorithms for it are very valuable contributions for many areas of tech.

fishfaselltoday at 4:02 AM

It would be cool to see agentic interpretation of function and variable names. It can see and track the flow of data a lot faster than a human can so if given some context, maybe it could synthesize names for them.

show 1 reply
ur-whaletoday at 9:21 AM

Not sure why someone would want to use an LLM to build a new decompiler instead of training an LLM to BE a decompiler.

Especially given the fact that you have an infinite training set to train that LLM from (compilers can generate as much training data as you could possibly want).

show 1 reply
DobarDabartoday at 4:17 AM

[dead]