From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2454 invoked by alias); 17 May 2010 21:04:41 -0000 Received: (qmail 2378 invoked by uid 22791); 17 May 2010 21:04:40 -0000 X-SWARE-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 May 2010 21:04:32 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o4HL4VMA019851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 17 May 2010 17:04:31 -0400 Received: from zebedee.pink (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o4HL4TW8025602; Mon, 17 May 2010 17:04:30 -0400 Message-ID: <4BF1AF5D.3050807@redhat.com> Date: Mon, 17 May 2010 21:04:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: gcc@gcc.gnu.org Subject: Re: Design Considerations of GIMPLE Front End References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg00311.txt.bz2 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 > > (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.