This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Separating c++ parser
- From: Ashwin Bharambe <ashwinb at gmail dot com>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 12 Sep 2005 15:30:10 -0400
- Subject: Separating c++ parser
- Reply-to: ashwinb at gmail dot com
Hi all,
I intend to use gcc's C++ parser and the intermediate representation
it creates for use in source browsing, etc. I have a few questions
regarding this: firstly, is it possible to plug out the parser and
intermediate representation code (presumably only in the front-end?)
relatively easily? If so, can somebody offer hints on where I could
start? I am currently looking into the gcc/cp front-end subdirectory,
but clearly, there are a number of dependencies inside the main gcc
code as well.
The other question is: the build process for gcc is quite hairy -
stage1, etc. etc. Since I am not concerned with code generation or
optimization at all, I don't think I would need this. How would I
begin simplifying the auto* and Makefile.in's to allow building the
parser as a stand-alone entity?
Thanks in advance for any help or pointers!
Ashwin
--
Ashwin Bharambe, Ph.D. Candidate, Carnegie Mellon University.
Office: 412-268-7555 Web: http://www.cs.cmu.edu/~ashu