From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19360 invoked by alias); 19 Jan 2004 17:51:37 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 19346 invoked from network); 19 Jan 2004 17:51:36 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 19 Jan 2004 17:51:36 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id i0JHpYl31141; Mon, 19 Jan 2004 12:51:34 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i0JHpXa04288; Mon, 19 Jan 2004 12:51:33 -0500 Received: from dnovillo.cipe.redhat.com (dnovillo.cipe.redhat.com [10.0.0.106]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id i0JHpVXd029165; Mon, 19 Jan 2004 12:51:32 -0500 Subject: Re: [RFC] Contributing tree-ssa to mainline From: Diego Novillo To: Geert Bosch Cc: Jan Hubicka , "gcc@gcc.gnu.org" , Richard Kenner In-Reply-To: References: <10401191226.AA27734@vlsi1.ultra.nyu.edu> <1074516514.5368.191.camel@frodo.toronto.redhat.com> Content-Type: text/plain Organization: Red Hat Canada Message-Id: <1074534670.25137.101.camel@frodo.toronto.redhat.com> Mime-Version: 1.0 Date: Mon, 19 Jan 2004 17:51:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg01314.txt.bz2 On Mon, 2004-01-19 at 12:42, Geert Bosch wrote: > There are many cases where we need to expand the original code in order > to generate checks. Some Ada constructs generate a non-trivial amount of > code, with calls to the Ada run time library, exception handlers etc. > Once we expand such code, it is unlikely it could be optimized away. > I agree with Richard that we need optimize away such constructs as early > as possible, which is in the front end before expansion. > Instead of emitting runtime calls, would it be possible to emit tree codes with well defined semantics? On finding them, the optimizers would know that it's not just an arbitrary function call for instance (perhaps adding attributes to the libcall). But I'm oversimplifying. We would have to talk about specific cases. Diego.