This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: loading output of -fdump-tree-original-raw
- From: Steven Bosscher <stevenb dot gcc at gmail dot com>
- To: "Marcus G. Daniels" <mdaniels at lanl dot gov>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 28 May 2010 09:46:45 +0200
- Subject: Re: loading output of -fdump-tree-original-raw
- References: <4BFF36BC.8010906@lanl.gov>
On Fri, May 28, 2010 at 5:21 AM, Marcus G. Daniels <mdaniels@lanl.gov> wrote:
> Hi all,
>
> For the purposes of static analysis, can the output of
> -fdump-tree-original-raw complete for reconstructing GENERIC data?
To reconstruct GIMPLE completely? No. All data types definitions are
missing, for example.
Depending on what you are trying to do, and how close (or far away)
you have to be from the source language, I think you have three
options:
1. -fdump-parse-tree for a complete dump of the gfortran
interpretation of the source code. Very close to the source language.
Contains all types, declarations, where they come from, and all
statements. Array syntax not lowered.
2. As part of the "gimple front end" GSoC project
(http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/gcc/t127230758645)
there will probably be textual representation of GIMPLE, that you can
perhaps import for static analysis. This is one level after GENERIC
and far away from the source language, has control flow, array syntax
lowered, etc.
3. a plugin a la dehydra, which is complex but does show the potential
of plugins for static analysis
Hope this helps,
Ciao!
Steven