From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-65472-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 1070 invoked by alias); 31 Dec 2002 16:48:10 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 1062 invoked from network); 31 Dec 2002 16:48:09 -0000
Received: from unknown (HELO smtp03.iprimus.com.au) (210.50.30.52)
  by 209.249.29.67 with SMTP; 31 Dec 2002 16:48:09 -0000
Received: from smtp02.iprimus.net.au (210.50.76.70) by smtp03.iprimus.com.au (6.7.010)
        id 3E0FA3A20001D403 for gcc@gcc.gnu.org; Wed, 1 Jan 2003 03:47:57 +1100
Received: from localhost.iprimus.com.au ([203.134.93.129]) by smtp02.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600);
	 Wed, 1 Jan 2003 03:47:56 +1100
Message-Id: <5.1.0.14.0.20030101033946.009f3c70@pop.iprimus.com.au>
X-Sender: jamesbuch@pop.iprimus.com.au
Date: Tue, 31 Dec 2002 10:32:00 -0000
To: Daniel Jacobowitz <drow@mvista.com>
From: James Buchanan <jamesbuch@iprimus.com.au>
Subject: Re: New front end, help needed
Cc: gcc@gcc.gnu.org
In-Reply-To: <20021231162238.GA29737@nevyn.them.org>
References: <5.1.0.14.0.20030101031203.009f2a00@pop.iprimus.com.au>
 <5.1.0.14.0.20030101031203.009f2a00@pop.iprimus.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 31 Dec 2002 16:47:57.0305 (UTC) FILETIME=[5F09E690:01C2B0EC]
X-SW-Source: 2002-12/txt/msg01646.txt.bz2

At 11:22 AM 12/31/2002 -0500, Daniel Jacobowitz wrote:
>You should take a good look at "treelang", which is the sample
>frontend, and also a good look at the GCC Internals manual (gccint.info
>in gcc/doc/ in a built tree).

Thanks for this.  I can get the gccint manual on the website,
I just went and had a look.

I've already seen treelang, but it wasn't very helpful for me.  I was
looking for more of something that starts from the very beginning.
It already requires a good knowledge of GCC internals because
I can't fully understand it.  I suppose I need to fill in the gaps myself
and keep going back for another look until it falls into place. :-)

Cheers
James