Diego Novillo wrote:
On Mon, Oct 13, 2008 at 14:25, Reza Roboubi <reza@xxxxxxxxxx> wrote:
Can we get a better view of what the optimizer is doing, such as some hint
of which data values represent which variables inside the original C-code?
Try using -fdump-tree-all in GCC versions starting with 4.0.
This looks like exactly what I need. It's great! Right down to
temporary variables' exact memory locations :-)
Boy, reading gcc optimized code is actually a fun thing to do, it seems!
Thank you so much Diego.
Reza.
