Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Reverse engineering can be as simple as, hey this code is supposed to be fast but it's slow, and I wonder what the compiler is doing to my code. So you compile the code, reverse engineer it and see what the compiler is emitting. That way you can steer the compiler into the right path. This is very useful for micro optimizations.


Just save the intermediate assembly files, with all helpful annotations, and analyze those. Much easier!


Once you are used to reading assembly, there's not much difference between reading the output of objdump -d and gcc -S.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: