From: Diego Novillo <dnovillo@google.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc <gcc@gcc.gnu.org>, Sandeep Soni <soni.sandeepb@gmail.com>
Subject: Re: Design Considerations of GIMPLE Front End
Date: Tue, 18 May 2010 15:04:00 -0000 [thread overview]
Message-ID: <AANLkTimwVOdoTbzpqwHRcyq8EgyssQCsk-nmAHgvLeoH@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilQWdLDrQypzwqbzTKsUYKyPKMvHMKVClFvZJWH@mail.gmail.com>
[ apologies for the duplicate message. My previous reply was bounced
by the ML. ]
> On Tue, May 18, 2010 at 10:52, Andrew Haley <aph@redhat.com> wrote:
>>
>> On 05/18/2010 04:05 PM, Dave Korn wrote:
>> > On 18/05/2010 15:17, Steven Bosscher wrote:
>> >
>> >> IMHO, ideally we would have a syntax that is human readable and human
>> >> writable. S-expressions are not as easy to read for me as something
>> >> that resembles C.
>> >
>> > I'd like it that way too, but I acknowledge that it would be more work and
>> > it's not me who'd have to do that extra work...
>>
>> Well, it can always be changed later, but there's a lot to be said for
>> not spending time now writing a parser, and getting on with the project.
>> It's a matter of taste anyway.
>
Yup. This shade of blue can be changed later. Sandi, let's start
with the S-expression syntax for everything. Richard is correct in
pointing out that even gimple expressions have metadata associated
with them that will need to be represented.
Diego.
next prev parent reply other threads:[~2010-05-18 15: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
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 [this message]
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=AANLkTimwVOdoTbzpqwHRcyq8EgyssQCsk-nmAHgvLeoH@mail.gmail.com \
--to=dnovillo@google.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=soni.sandeepb@gmail.com \
/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).