News for hackers. Stuff that matters.
Re:How decompilers work by T-R on Thursday May 05, 2011 @02:36PM (#2518438)
Have you tried applying any of this to (segments of) 68k binaries?

You mentioned that a decompiler would have been only slightly useful for older games written in C/C++; is flow analysis not helpful in practice for simplifying code that was originally hand-coded in assembly?

Edit1: Thanks for the link to the paper[1], by the way. Do you know of any other good resources?

Edit2: Nevermind, I see you have them in github[2]. Thanks again.

[1] http://www.ci.tuwien.ac.at/~grill/decompilation_thesis.pdf [2] https://github.com/drx/ocd

Re:How decompilers work by drx on Thursday May 05, 2011 @02:50PM (#2518495)
I've started writing a 68k ASM module a while ago but I never finished.

Hand-coded assembly code is better in that it's less optimized and mangled. But worse in that it has much less structure -- I can't convert ASM code into C. Each programmer has its own way of implementing certain programming patterns, etc.

IDA Pro is actually quite good at flow analysis of ASM code.

Re:How decompilers work by drx on Thursday May 05, 2011 @05:24PM (#2518970)
As I can't edit my post any more, and you don't have an email address in your profile, I will double post.

> Do you know of any other good resources?

The thesis has many references, I would start with that.