From: Ian Lance Taylor <iant@google.com>
To: charfi asma <charfiasma@yahoo.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [GCC front end] add new TREE CODE
Date: Mon, 14 Feb 2011 17:48:00 -0000 [thread overview]
Message-ID: <mcr4o86bj9g.fsf@google.com> (raw)
In-Reply-To: <64888.39441.qm@web28511.mail.ukl.yahoo.com> (charfi asma's message of "Mon, 14 Feb 2011 16:43:40 +0000 (GMT)")
charfi asma <charfiasma@yahoo.fr> writes:
> I am developping my own gcc front end. My source language contains concepts that
> are not represented directly in C code.
> to compile those elements, I think that I should add a new tree codes to my
> front end as C++ does for templates...
> I think that I should also implement how to translate this new tree code in
> Gimple.
> my question is : should I also care about how to translate those tree code al
> over the compiler chain: gimple --> ssa --> unssa --> rtl --> ass ...
> did you suggest to follow an example of an existing front end that adds some
> tree code cause the C++ one seems to be mature and complete.
First let me say that if your language is very different from C you
probably shouldn't be using trees at all.
But if your language is mostly like C then using trees is reasonable.
Even the C frontend itself has language-specific tree codes; see
c-family/c-common.def. Or look at Objective C, at objc/objc-tree.def.
Ian
next prev parent reply other threads:[~2011-02-14 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 17:44 charfi asma
2011-02-14 17:48 ` Ian Lance Taylor [this message]
2011-02-14 23:59 ` Andi Hellmund
2011-02-21 11:26 ` Re : " charfi asma
2011-02-21 14:27 ` Andi Hellmund
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=mcr4o86bj9g.fsf@google.com \
--to=iant@google.com \
--cc=charfiasma@yahoo.fr \
--cc=gcc-help@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).