From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3231 invoked by alias); 20 May 2003 12:33:36 -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 3156 invoked from network); 20 May 2003 12:33:35 -0000 Received: from unknown (HELO its-mu-earth.its.rmit.edu.au) (131.170.2.10) by sources.redhat.com with SMTP; 20 May 2003 12:33:35 -0000 Received: from its-mn-inet1.its.rmit.edu.au (ems.rmit.edu.au [131.170.10.112]) by its-mu-earth.its.rmit.edu.au (8.10.1/8.10.1/ANTI-SPAM/ANTI-RELAY/EARTH) with ESMTP id h4KCXWC03771 for ; Tue, 20 May 2003 22:33:32 +1000 (EST) Received: from INET1-MTA by its-mn-inet1.its.rmit.edu.au with Novell_GroupWise; Tue, 20 May 2003 22:33:33 +1000 Message-Id: Date: Tue, 20 May 2003 13:27:00 -0000 From: "Marty Hauff" To: Cc: Subject: Re: [tree-ssa] Any good sources of documentation? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-SW-Source: 2003-05/txt/msg01858.txt.bz2 >Hardware resources? I'm not sure I follow. There is >nothing >hardware-related in trees. Just FYI... When developing a new application, most programmers have a fai= r idea about what processor they are going to use. In the high volume embe= dded world, however, it may not be clear which is the best cost/performance= architecture to use. What I am trying to research is a methodology that w= ill specify the best hardware to use based on the functionality requested b= y the application code. From what I understand of the compilation process = in GCC, trees are the latest point during compilation prior to machine spec= ific constructs being introduced. Once the code is converted to RTL it beg= ins to take on machine specific attributes - i.e. RTL is generated based on= the templates provided in the machine description file. In order to make = a non-prejudicial assessment of the best architecture for a given applicati= on, I can't use RTL because machine specific mappings and optimisations hav= e already taken place. It may be that the point at which first RTL convers= ion takes place may be the point I need to focus on but I'm still nutting t= hat one through. I am hoping to first extract sufficient information from = the trees to determine whether CISC or RISC is appropriate and then whether= an 8/16/32/64 bit architecture is best, how many registers and what sort a= nd how many ALUs and what functionality. All very interesting but bloody hard! Enjoy Marty If you find yourself going through hell ... keep going!