|GCC -fdump-translation-unit .tu file format email@example.com (firstname.lastname@example.org) (2008-10-14)|
|Re: GCC -fdump-translation-unit .tu file format email@example.com (Diego Novillo) (2008-10-15)|
|Re: GCC -fdump-translation-unit .tu file format firstname.lastname@example.org (Pertti Kellomaki) (2008-10-16)|
|Re: GCC -fdump-translation-unit .tu file format email@example.com (firstname.lastname@example.org) (2008-10-17)|
|Re: GCC -fdump-translation-unit .tu file format email@example.com (Armel) (2008-10-17)|
|From:||"Diego Novillo" <firstname.lastname@example.org>|
|Date:||Wed, 15 Oct 2008 18:53:24 -0400|
|Posted-Date:||15 Oct 2008 18:59:35 EDT|
On Wed, Oct 15, 2008 at 02:05, email@example.com <firstname.lastname@example.org> wrote:
> Help!!!Is there some one here who had been working on this field?
> Counld you give me some information where i can find the .tu file
> format???Or would you be so kind to tell me is there any other better
> way to extract the information from C++ source file???
There is little to no documentation about any of the dump files
emitted by GCC. We use them for debugging the compiler and not much
else. The .tu dump has been used by some folks to do some analysis,
but it is certainly not the intent to produce a complete dump of the
The best way to understand the format of the .tu file is to study the
source code of the particular version of GCC that you are working with
(tree-dump.c:dump_node is a good start). Different versions of GCC
may include different information in it.
Have you thought about hooking your analysis directly as a GCC pass?
Return to the
Search the comp.compilers archives again.