This is the mail archive of the gcc@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: Separating c++ parser


Hmm. Ok fine, I can live with having to keep all extraneous code lying
around. But it seems like there must be a way to:

 - stop gcc once the cp frontend parses the code and generates the
parse tree structure.
 - disable the stage1,stage2 compilation etc. during the build process? 

Or, is there something I am still missing? :)

Thanks,
Ashwin

On 9/12/05, Diego Novillo <dnovillo@redhat.com> wrote:
> On 09/12/05 15:30, Ashwin Bharambe wrote:
> 
> >is it possible to plug out the parser and intermediate representation code (presumably only in the front-end?) relatively easily?
> >
> Not really.  Though we have been re-designing the internal architecture
> to be more modular, all the components are meant to be used together.
> 
> At most, you could plug your own transformation/analysis inside the
> compiler.
> 


-- 
Ashwin Bharambe,  Ph.D. Candidate, Carnegie Mellon University.
Office: 412-268-7555            Web: http://www.cs.cmu.edu/~ashu


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