On 09/12/05 15:55, Ashwin Bharambe wrote:
- stop gcc once the cp frontend parses the code and generates the
parse tree structure.
Check -fsyntax-only.
- disable the stage1,stage2 compilation etc. during the build process?
just do 'make all' instead of 'make bootstrap'.
On Mon, 12 Sep 2005, Ashwin Bharambe wrote:
- disable the stage1,stage2 compilation etc. during the build process?
IIRC cross-compilers do not use stage1/2/3 as it is not possible to
execute produced target binary on the host platform. And for compiling
cross-compiler simple `make' is used.
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 front
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 s
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
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?
