DCoder
15.11.2011, 08:02:36
OpenDune claims there are 1229 functions in the original game.
IDA tells me there are 18355 functions in YR 1.001. This includes piles of template specializations, thunks, CRT functions and other crap, but still, it's 15x the size.
The largest function in the game is BuildingTypeClass::LoadFromINI, at 19475 bytes.
How do you imagine this recompiled stuff should be connected to the game? Replace the first instruction of the original function with a JMP to the new one? Syringe can do that.
Assembly output should be fairly simple with IDA - last weekend I started writing (for other purposes) an IDA plugin to spit out the asm instructions from a function without any decorations IDA normally places around them, wrapping that in __asm {} would be all that's needed for a start. But I really doubt that that approach would get you comprehensible code faster than Hex Rays does.
IDA tells me there are 18355 functions in YR 1.001. This includes piles of template specializations, thunks, CRT functions and other crap, but still, it's 15x the size.
The largest function in the game is BuildingTypeClass::LoadFromINI, at 19475 bytes.
How do you imagine this recompiled stuff should be connected to the game? Replace the first instruction of the original function with a JMP to the new one? Syringe can do that.
Assembly output should be fairly simple with IDA - last weekend I started writing (for other purposes) an IDA plugin to spit out the asm instructions from a function without any decorations IDA normally places around them, wrapping that in __asm {} would be all that's needed for a start. But I really doubt that that approach would get you comprehensible code faster than Hex Rays does.