3 ms·
He just knew the instruction codings and what not to use - e.g., "sub al, al" instead of "mov al, 0". He knew all of those by heart. Both in hex and in decimal.
by beagle3 16y ago
He just knew the instruction codings and what not to use - e.g., "sub al, al" instead of "mov al, 0". He knew all of those by heart. Both in hex and in decimal.
(Me, I was able to read machine code from hex, but not write it unless it was extremely simple; and the hex<->dec conversion took too long. So I just used debug for those 10-20 instruction things)
- kragen 16y agoI see. After playing with this for a bit today (see http://lists.canonical.org/pipermail/kragen-hacks/2011-April/000519.html http://lists.canonical.org/pipermail/kragen-hacks/2011-April...) it seems like forward calls, immediate zeroes, 16-bit immediate operands with a zero byte, and doing an OR or an ADD with AL as the source operand are among the enemies to avoid. It's still kind of magical to me to write a program that does something useful that's only half a line of gibberish when you TYPE it. I just wish there was a better way than PNG to share what it's supposed to look like!