Artem Shinkarov <artyom.shinkar...@gmail.com> writes:

> That is why now I want to use a gcc code-base for solving the same
> task. And the main problem for me at the moment is to build a cpp
> binary which would be able to handle options for preprocessor but
> which would not pull so many code from middleend and backend. In other
> words I want to have a separate binary for cpp.

Why?

I concede that the fact that cpp invokes the whole compiler is a bit
ugly and perhaps slightly inefficient.  But it's not all that bad and it
does work today.  The goals of your project seem entirely separable from
the goal of having a single cpp binary.

Ian

Reply via email to