TREE & RTL (intermediate code) documentation

[Jim Wilson]

fpuentes@udc.es wrote:
> (memory to memory) but it is better idea to use GCC as an inline generator, 
> embedding GCC as a library (changing toplev.c). But i have other idea, to make 
> a <generic> front-end which is used directly from other codes (my code generate 
> a TREE data and pass it to an adecuate GCC function). Well, the case is I need 
> TRR documentation and RTL too, and if you could help me in somethigs task (only 
> support by email, anwser questions, only).

You may find the gcc design inconvenient for this.  It has long been FSF 
policy to make it hard for others use parts of GCC, for fear that people 
would then write proprietary front-ends or optimizations passes for gcc. 
  A side effect of this is that many interfaces are not as clean as they 
could be.  Hopefully this will change in the future, but it is unclear 
when.  Some improvements are already on the tree-ssa branch.

There is quite a bit of info about trees and rtl in our documentation. 
There are gcc/doc/*.texi files in the source code for producing manuals. 
  There are also manuals on the web, e.g.
	http://gcc.gnu.org/onlinedocs/gccint/
It isn't very readable though, it is more useful as a reference.

Writing your own front end is very uncommon, and likely to be a lot of work.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com