From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25445 invoked by alias); 18 May 2010 08:39:18 -0000 Received: (qmail 25435 invoked by uid 22791); 18 May 2010 08:39:17 -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; Tue, 18 May 2010 08:39:09 +0000 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o4I8d6Su010292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 18 May 2010 04:39:06 -0400 Received: from zebedee.pink (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o4I8d57p016550; Tue, 18 May 2010 04:39:05 -0400 Message-ID: <4BF25228.1000005@redhat.com> Date: Tue, 18 May 2010 08:39: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: <4BF1AF5D.3050807@redhat.com> 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/msg00314.txt.bz2 On 05/18/2010 04:24 AM, Sandeep Soni wrote: > On Tue, May 18, 2010 at 2:34 AM, Andrew Haley wrote: > >>> 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. > > Thanks Andrew . Any thoughts on the 3rd point? Your suggestion for 3 is perfectly sensible, and is a good way to start. It's quite possible that, whatever you do, you'll find that the file structure will need to be changed, so it makes sense to do something as simple and straightforward as possible. If your code is well-factored it can be reorganized later. Andrew.