From: Andrew Haley <aph@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: Design Considerations of GIMPLE Front End
Date: Mon, 17 May 2010 21:04:00 -0000 [thread overview]
Message-ID: <4BF1AF5D.3050807@redhat.com> (raw)
In-Reply-To: <AANLkTinl4LsRATSj0LtJPJIHUV02S8vSHmufYBKzld86@mail.gmail.com>
On 05/17/2010 09:15 PM, Sandeep Soni wrote:
> Hi,
>
> As part of GSoC 2010, I am developing a front end for GIMPLE.
> You can find the basic theme of the project at:
> http://gcc.gnu.org/wiki/GimpleFrontEnd
>
> One of the most important components in this GIMPLE Front End is to
> convert the GIMPLE tuples into text.
> How such a textual representation should be, will obviously dictate
> the design and complexity of the
> subsequent parsing component. So, as per Diego's suggestion, to have a
> view on some of the issues
> I have started this thread.
>
> Following are some of the issues/questions that have come up:
>
> 1. What should be the format of representation of the GIMPLE tuples in text?
>
> Ideally, the textual representation should be satisfying two goals:
> Easy to parse and easy for a programmer
> to write by hand.Considering this,what is the best way in which the
> GIMPLE tuples be represented.
>
> For example:
> A textual GIMPLE tuple for the statement a=b+c can be like
> <GIMPLE_ASSIGN<PLUS_EXPR,a,b,c>> (As demonstrated by the internal
> manual also).
> Is such a representation easy to parse?
S-expressions are easier to parse and more compact, and are consistent
with gcc's back end. Also, there are editors that already know how to
edit and indent S-expressions.
Andrew.
next prev parent reply other threads:[~2010-05-17 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 20:21 Sandeep Soni
2010-05-17 21:04 ` Andrew Haley [this message]
2010-05-18 3:25 ` Sandeep Soni
2010-05-18 8:39 ` Andrew Haley
2010-05-18 13:18 ` Diego Novillo
2010-05-18 14:00 ` Michael Matz
2010-05-18 14:09 ` Diego Novillo
2010-05-18 14:18 ` Steven Bosscher
2010-05-18 14:46 ` Dave Korn
2010-05-18 14:52 ` Andrew Haley
[not found] ` <AANLkTilQWdLDrQypzwqbzTKsUYKyPKMvHMKVClFvZJWH@mail.gmail.com>
2010-05-18 15:04 ` Diego Novillo
2010-05-18 15:24 ` Sandeep Soni
2010-05-18 14:30 ` Basile Starynkevitch
2010-05-18 14:32 ` Richard Guenther
2010-05-18 14:47 ` Steven Bosscher
2010-06-04 8:24 ` Sebastian Pop
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=4BF1AF5D.3050807@redhat.com \
--to=aph@redhat.com \
--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).