How do decompilers work in general? I'm imagining the normal compiler pipeline in reverse: convert the machine code into some intermediate representation, add some 'de-optimization' passes to make the control flow more clear, then a back end which converts that into a C AST, which is then printed out into valid C code.
Anyone know how this compares to the industry-standard Hex-Rays Decompiler? (Sold as an add-on to IDA Pro)
Closed source, windows only, diss-assmebles 6502 only, and expires next month. No thanks.
I'd be curious to see what C it produced if you fed it hand-written assembly.
guess what guys davido hkn gang rap and win competition form is now out on sales for purchase please call joseph on 08166840624 and also call for booking and reservation of seat dont miss out
guess what guys davido hkn gang rap and win competition form is now out on sales for purchase please call joseph on 08166840624 and also call for booking and reservation of seat dont miss out
Just this week I was exploring C decompilers and stumbled upon the open source Snowman[0], which worked well for my purposes and can run in a self contained mode with a dependency on Qt5.
[0] https://github.com/yegord/snowman