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: The tree API


Rafael Espíndola <rafael.espindola@gmail.com> writes:

> On 6/16/05, ibanez@sunplus.com.tw <ibanez@sunplus.com.tw> wrote:
> > 
> > 
> > 
> > 
> > Hello~ every one :)
> > 
> > I'm a new guy in gcc mailing list
> > I've been studying gcc for 2 months.
> > I read "GNU compiler collection internals" (for GCC 3.5.0?),
> > and I also trace the source code for target-mips.
> > My problem is there are so much symbol/function/API in gcc.
> > Some are documentated in the book but not all of them.
> > All I can do is modified it, rebuild and see what's happend.
> > This approach is not effective.
> > If there is a way to learn the gcc internal APIs "systematically"?
> 
> I think that I can help since I am having the same problem :)
> 
> The best references that I can give you is the GCC Frontend HOWTO at
> http://www.tldp.org/HOWTO/GCC-Frontend-HOWTO.html. It is based on a
> old gcc, but most of the tree structure still applies.

 Don't forget the GENERIC and GIMPLE documentation at
http://gcc.gnu.org/onlinedocs/gccint/Tree-SSA.html#Tree-SSA
 
> Two colleges and I are working on a minimal "hello world" front end
> for gcc. You can find a alpha version at
> http://ltc08.ic.unicamp.br/svn/scheme/branches/hello-world
> 
> I also recommend that you take a look at treelang. It is quite simpler
> than the others frontends in gcc.
> 
> I hope this helps,
> Rafael Ávila de Espíndola
> 


-- 
Thanks,
Jim

http://www.csclub.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim


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