News for hackers. Stuff that matters.

A comment on Bootable Minecraft clone written partly in x86 Assembly. Parent comment

Re:Bootable Minecraft clone written partly in x86 Assembly by 6ren on Monday June 17, 2013 @10:41AM (#5893419)
He doesn't say anything about decompiling.

  > Then I began slowly porting everything to handwritten assembly.
[ Parent | on HN ]
Re:Bootable Minecraft clone written partly in x86 Assembly by 300bps on Monday June 17, 2013 @11:36AM (#5893764)
>Starting in assembly right away would be a bit too insane, so I first wrote a reference implementation in C

How did he make the reference code? I'm reading that as he wrote an implementation in C, then decompiled it and then cleaned up the decompiled Assembly language code.

Maybe I'm wrong. How do you take his statement above?

[ Parent | on HN ]
Re:Bootable Minecraft clone written partly in x86 Assembly by Overv on Monday June 17, 2013 @03:07PM (#5895220)
Author here, I did look at some of the assembly output from C code, especially for frequently called functions like get_block/set_block, but other than that I used no reference but the original C code to write the assembly.
[ Parent | on HN ]
Re:Bootable Minecraft clone written partly in x86 Assembly by icegreentea on Monday June 17, 2013 @11:59AM (#5893908)
You can also read it as, write C code, test. Repeat until you have functionality you want. Pick block of C code, replace with assembly equivalent. Repeat.
[ Parent | on HN ]
Re:Bootable Minecraft clone written partly in x86 Assembly by drv on Monday June 17, 2013 @12:32PM (#5894104)
He probably asked the compiler to emit the assembly it generates (e.g. gcc's -S option); disassembling or decompiling would be overkill.
[ Parent | on HN ]
Re:Bootable Minecraft clone written partly in x86 Assembly by jdefr89 on Monday June 17, 2013 @12:32PM (#5894105)
He COMPILED the C code into its assembly stage with a gcc option. He probably just looked at the .S file from gcc..
[ Parent | on HN ]