This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building GENERIC trees
- From: Tom Crick <cs1tc at bath dot ac dot uk>
- To: "" <gcc at gcc dot gnu dot org>
- Cc: Paul Brook <paul at codesourcery dot com>
- Date: Mon, 12 Apr 2004 00:44:08 +0100
- Subject: Re: Building GENERIC trees
- References: <002501c40853$efae45a0$0200a8c0@tcrick> <200403121724.56395.paul@codesourcery.com>
Quoting Paul Brook <paul@codesourcery.com>:
> > > Hi again, the thing about GENERIC is that it's not all that
> > > documented, however there were a thread about this a while
> > > ago on the gcc mailinglist, search through the archives and
> > > you will find a mail which states ' if it's not in these
> > > files then it's not GENERIC, ( and some files are named, fx.
> > > tree.h and some more ). I dare not give you an answer
> > > straight from my head because the probability of error is too large.
>
> tree.def contains a definitions of the tree nodes, tree.h contains macros for
> accessing them.
Hi all,
Apologies for replying to an old(ish) post, but wanted to ask some follow-up
questions after looking at tree.h and tree.def:
Where can I find the conversion of C trees into GENERIC (the famous 'genericize'
function), as I would like to build from this to see how I could build GENERIC
trees for BCPL.
Once GENERIC trees are built (in this case, probably for a subset of the BCPL
language), how do you go about linking them into the GCC chain - how do you
'latch-on' to the 'gimplification' and then into the back end?
Also, are there any plans for better documentation of GENERIC and GIMPLE e.g.
giving language definitions or a 'how to build GENERIC trees' guide? :-)
Thanks for your help.
Regards,
Tom
--
BCPL for GCC
http://sourceforge.net/projects/gccbcpl/