public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jeremias A. Sauceda" <pi314@iastate.edu>
To: gcc-help@gcc.gnu.org
Subject: AST to XML
Date: Sun, 18 Mar 2001 00:04:00 -0000	[thread overview]
Message-ID: <3AB46C2E.32C65CE0@iastate.edu> (raw)

Hello,

I am a research assistant at Iowa State's Software Reengineering Lab.
Last semester I created a program to convert Edison Design Group's
Intermediate Language files (an Abstract Syntax Tree) into XML.
Unfortunately their C/C++ front end does not support many gcc
extensions.  I would like to use GCC's front end instead, since it
obviously support gcc extensions and is open source.  I desperately need
gcc extensions since I am analyzing the Linux Kernel, which is very
biased to gcc.

There are two reasons why EDG's front end was chosen.  The abstract
syntax tree it creates is a complete representation of the source code,
no optimizations are done.  We received the full source code (after
signing an NDA).  We need a pristine representation of the source code
since we are doing high level analysis of code; for automatic MPI
parallelization, slicing, etc.

By glancing through tree.h and tree.def I think that most of the
information I need is present except for line and column numbers.  I
need at least the block start and end points, preferably those of
statements, optimally of all expression terminals.  Is this already in
the tree?  What do I have to do to add it?

Ultimately I would like to create an XML backend to gcc.  So instead of
an object file I get an XML AST.  What do you think?

Thanks,

Jeremias Sauceda

                 reply	other threads:[~2001-03-18  0:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AB46C2E.32C65CE0@iastate.edu \
    --to=pi314@iastate.edu \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).