public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandeep Soni <soni.sandeepb@gmail.com>
To: GCC LIST <gcc@gcc.gnu.org>
Subject: Re: Design Considerations of GIMPLE Front End
Date: Tue, 18 May 2010 03:25:00 -0000	[thread overview]
Message-ID: <AANLkTimsmkCuKWTZcM24QiZtb5HjpSs2yCTkliRcvZ1G@mail.gmail.com> (raw)
In-Reply-To: <4BF1AF5D.3050807@redhat.com>

On Tue, May 18, 2010 at 2:34 AM, Andrew Haley <aph@redhat.com> wrote:

>>    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.

Thanks Andrew . Any thoughts on the 3rd point?

>
> Andrew.
>



-- 
Cheers
Sandy

  reply	other threads:[~2010-05-18  3:25 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
2010-05-18  3:25   ` Sandeep Soni [this message]
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=AANLkTimsmkCuKWTZcM24QiZtb5HjpSs2yCTkliRcvZ1G@mail.gmail.com \
    --to=soni.sandeepb@gmail.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).