From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11366 invoked by alias); 22 Jun 2004 20:37:30 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 11359 invoked from network); 22 Jun 2004 20:37:29 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.5) by sourceware.org with SMTP; 22 Jun 2004 20:37:29 -0000 Received: (qmail 31266 invoked from network); 22 Jun 2004 20:37:28 -0000 Received: from localhost (HELO codesourcery.com) (mitchell@127.0.0.1) by mail.codesourcery.com with SMTP; 22 Jun 2004 20:37:28 -0000 Message-ID: <40D8988B.3060109@codesourcery.com> Date: Tue, 22 Jun 2004 21:12:00 -0000 From: Mark Mitchell Organization: CodeSourcery, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Richard Kenner CC: gcc-patches@gcc.gnu.org Subject: Re: Patch to allow Ada to work with tree-ssa References: <10406222028.AA10260@vlsi1.ultra.nyu.edu> In-Reply-To: <10406222028.AA10260@vlsi1.ultra.nyu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg01796.txt.bz2 Richard Kenner wrote: > Since Richard Henderson and Zack seem to think it's best, why don't you > just create new tree nodes for these variable-length cases? That seems > to be the consensus point of view on how to solve the problem. > >Except that the authors of the optimizers haven't weighed in here yet >and they were very much against adding new nodes to GIMPLE, which is >what this would be doing. Having played with some of that code, I can >tell you that it won't be pleasant to add all the extra cases to >deal with the additional nodes. > >Also, I'm told that over on IRC, the Fortran folks have ideas about >what to do with some of the new fields. > >I think the memory cost argument in GIMPLE is very weak: only a very >tiny fraction of GIMPLE nodes are ARRAY_REF and COMPONENT_REF. > >Your arguments about trees that are permanently kept around at the >GENERIC level seems a far stronger argument and that's why I was thinking >about having a different node for front-end use that corresponds to >the shorter form. > > Well, that's certainly a place to start. If you have both nodes, you can decide where to use one and where to use the other. If you want to transition from the short form to the long form in the gimplifier, I think we can compromise on that. -- Mark Mitchell CodeSourcery, LLC (916) 791-8304 mark@codesourcery.com