| |||||||||||||
Rethinking optimization for sizeRethinking optimization for sizePosted Feb 11, 2013 21:09 UTC (Mon) by PaXTeam (subscriber, #24616)In reply to: Rethinking optimization for size by Aliasundercover Parent article: Rethinking optimization for size
maybe you want gcc -S -fverbose-asm for commented assembly output? also -fdump-tree-all and -fdump-rtl-all if you want to see what happens to your C and also relate the internal GIMPLE variable names to the comments in the verbose asm output.
(Log in to post comments)
Rethinking optimization for size Posted Feb 12, 2013 16:28 UTC (Tue) by Aliasundercover (subscriber, #69009) [Link]
Well, you got me there. I tried those dump options and got 151 spam files in my source directory.
-fverbose-asm seems useful. It doesn't help with finding where my code went but the comments are nice.
I wish compiler listings got more respect.
|
|||||||||||||