Separating c++ parser
Fariborz Jahanian
fjahanian@apple.com
Mon Sep 12 20:03:00 GMT 2005
You can start off by looking into how -fsyntax-only option is
implemented.
- fariborz
On Sep 12, 2005, at 12:55 PM, Ashwin Bharambe wrote:
> 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
>
More information about the Gcc
mailing list