From: Andi Hellmund <mail@andihellmund.com>
To: charfi asma <charfiasma@yahoo.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Re : [GCC front end] add new TREE CODE
Date: Mon, 21 Feb 2011 14:27:00 -0000 [thread overview]
Message-ID: <4D627092.2060409@andihellmund.com> (raw)
In-Reply-To: <741091.71307.qm@web28516.mail.ukl.yahoo.com>
>
> Ian said in his response that if my language is very different than C I should
> not use trees. Have you any idea of what I can use instead ?
>
>
Hey Asma,
I'm not sure what Ian meant in detail, but I think that he wanted to say
that you then shouldn't possibly use the TREE codes and
tree-representation of GCC, but to use whatever intermediate
representation is appropriate for your needs. If you would look up the
literature, you would find tree-based structures as dominant
intermediate structure, but most of these books then refer to
C-syntax-like languages. Though, it is generally hard to predict which
structure perfectly matches your needs. As said, you could use whatever
you want. All you need to make sure is to finally translate to GIMPLE at
some point.
> I look at the ghdl front end and I did not find vhdl-tree.def to see if they
> defined a new tree code for this fe.
>
This file is not mandatory, I think. So, if they don't use one, they
might not use additional tree codes. Well, if they use GENERC/tree-based
IR at all!
Best regards,
Andi
prev parent reply other threads:[~2011-02-21 14:03 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
2011-02-21 11:26 ` Re : " charfi asma
2011-02-21 14:27 ` Andi Hellmund [this message]
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=4D627092.2060409@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).