From: "S. Bosscher" <S.Bosscher@student.tudelft.nl>
To: "'dima@pulsepow.hop.stu.neva.ru'" <dima@pulsepow.hop.stu.neva.ru>
Cc: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Re: An ask for documentation of trees
Date: Mon, 21 Oct 2002 11:38:00 -0000 [thread overview]
Message-ID: <4195D82C2DB1D211B9910008C7C9B06F01F372D0@lr0nt3.lr.tudelft.nl> (raw)
> I'm currently developing a front-end for a language. I've read
> in the docs that using RTL for interfacing front-end and the bulk
> of GCC is a Bad Thing. And that trees should be used for it. So
> the question is: what should be done in the front-end to use
> trees? The language is not much similar to C, so some new types of
> tree nodes should be defined and implemented. How is this done?
> Thanks in advance.
1) Check out the tree-ssa branch, see the projects/tree-ssa/ for
information about this.
2) Have a look at the C++ front end.
3) Go see http://home.wanadoo.nl/btp91/gcc/gcc-ast.html. It's incomplete
but still useful.
4) Have a look at http://gcc.gnu.org/onlinedocs/gccint/, and read
http://gcc.gnu.org/onlinedocs/gccint/Trees.html#Trees. These pages
try to document what you can find in {tree, c-common, cp-tree}.{def,h}.
Hope this helps,
Greetz
Steven
next reply other threads:[~2002-10-21 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 11:38 S. Bosscher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 11:27 D. Adamian
2002-10-21 11:46 ` Fergus Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4195D82C2DB1D211B9910008C7C9B06F01F372D0@lr0nt3.lr.tudelft.nl \
--to=s.bosscher@student.tudelft.nl \
--cc=dima@pulsepow.hop.stu.neva.ru \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).