This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: "human readable" optimized code

From: Reza Roboubi <reza at parvan dot net>
To: Diego Novillo <dnovillo at google dot com>, gcc-help at gcc dot gnu dot org
Cc: Bob Plantz <plantz at cds1 dot net>
Date: Mon, 13 Oct 2008 21:35:48 -0700
Subject: Re: "human readable" optimized code
References: <48F392B2.8000303@parvan.net> <b798aad50810131211k744f9ea2q91f79dea2e4aae37@mail.gmail.com>

Diego Novillo wrote:

On Mon, Oct 13, 2008 at 14:25, Reza Roboubi <reza@parvan.net> 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.

References:
- "human readable" optimized code
  - From: Reza Roboubi
- Re: "human readable" optimized code
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]