C Programming Optimized Code, RAMifications
Let's take a look at what happens to our function when we compile it with compiler optimizations enabled. What is optimized code? What is function in-lining? See how the gcc compiler strips off the CDECL calling convention wrappers (stack push call and ret instruction overhead) and embeds our functions code directly into main() when we enable the gcc optimize for size flag, -Os.
This is just one of the many, many optimizing steps a compiler might do. We can also tell it to unroll loops, or treat the stack differently. See "man gcc" for options. But let's not enable too many of these optimizations, or risk ricing up our code.
Optimized code can run a little bit faster or take up a little bit less memory. However, the compiler flags we choose can make significant changes to the final assembly language output. This may not be a problem for some, but in the future we might want to know about this in case we decide to do some non-standard self-modifying code experiments.
Resources:
http://www.iso-9899.info/wiki/Main_Page
http://www.cs.princeton.edu/~benjasik...
http://www.phiral.net/linuxasmone.htm
http://en.wikibooks.org/wiki/Category...
http://en.wikipedia.org/wiki/X86_call...
Nesta página do site você pode assistir ao vídeo on-line C Programming Optimized Code, RAMifications duração hora minuto segundo em boa qualidade , que foi baixado pelo usuário Executive Quest 13 Março 2009, compartilhe o link com seus amigos e conhecidos, no youtube este vídeo já foi visto 8,059 vezes e gostou 22 espectadores. Boa visualização!
