From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32318 invoked by alias); 19 May 2003 13:22:09 -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 32285 invoked from network); 19 May 2003 13:22:08 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 19 May 2003 13:22:08 -0000 Received: from localhost (tornado.toronto.redhat.com [172.16.14.228]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 645A9800021; Mon, 19 May 2003 09:22:07 -0400 (EDT) Subject: Re: [tree-ssa] Any good sources of documentation? From: Diego Novillo To: Marty Hauff Cc: "gcc@gcc.gnu.org" In-Reply-To: References: Content-Type: text/plain Organization: Red Hat Canada Message-Id: <1053350593.19956.36.camel@frodo.toronto.redhat.com> Mime-Version: 1.0 Date: Mon, 19 May 2003 13:40:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg01750.txt.bz2 On Mon, 2003-05-19 at 04:22, Marty Hauff wrote: > I'm trying to find out how the tree-ssa branch performs its > compilation and optimisation. I've found the doxygen stuff on the web > but I need something a bit higher level at this stage. > Most documentation is in the source code itself. There is a high-level description of the optimization process in the project page (http://gcc.gnu.org/projects/tree-ssa/). After the GCC summit next week, I will post the tree SSA paper and slides in my home page. > Specifically I am looking to find a point during compilation where the > most optimisation has been done PRIOR to target specific processing > having been started. > tree-optimize.c:optimize_function_tree() > The main gcc branch is no good to me because it only does things on > a function by function basis. According to the docs, tree-ssa > processes the whole source _before_ generating rtl etc. (or have I got > this wrong?) > Both mainline and tree-ssa operate in the same way. If you use -funit-at-a-time, then compilation proceeds in call graph order. Diego.