From: Andi Hellmund <mail@andihellmund.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 23:59:00 -0000 [thread overview]
Message-ID: <4D596AEA.7030705@andihellmund.com> (raw)
In-Reply-To: <64888.39441.qm@web28511.mail.ukl.yahoo.com>
Hey Asma,
> my question is : should I also care about how to translate those tree code al
> over the compiler chain: gimple --> ssa --> unssa --> rtl --> ass ...
>
The idea of GCC's modularization is that a front-end should maximally
care about GIMPLE. All the other transformations are done by the
middle-end.
> 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.
>
Yes, the C++ front-end uses quite a lot of own TREE codes, but I would
then start with a very simple one and check how it "translates" the TREE
codes into a GIMPLE sequence, e.g. by looking at the 'gimplify_expr'
language hook which is 'cp_gimplify_expr' for C++.
I hope that helps. If you have any further question about the specific
transformation from TREE codes to GIMPLE, just let us know ...
Andi
next prev parent reply other threads:[~2011-02-14 17:48 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
2011-02-14 23:59 ` Andi Hellmund [this message]
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=4D596AEA.7030705@andihellmund.com \
--to=mail@andihellmund.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).