From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-92258-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 18924 invoked by alias); 5 Mar 2004 18:23:18 -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 18913 invoked from network); 5 Mar 2004 18:23:16 -0000
Received: from unknown (HELO shockwave.systems.pipex.net) (62.241.160.9)
  by sources.redhat.com with SMTP; 5 Mar 2004 18:23:16 -0000
Received: from nowt.org (81-178-235-206.dsl.pipex.com [81.178.235.206])
	by shockwave.systems.pipex.net (Postfix) with ESMTP id EDF0E1C0022B;
	Fri,  5 Mar 2004 18:23:15 +0000 (GMT)
Received: from finch.home (finch.home [192.168.1.6])
	by nowt.org (Postfix) with ESMTP
	id 3E85AAC92; Fri,  5 Mar 2004 18:23:15 +0000 (GMT)
From: Paul Brook <paul@codesourcery.com>
Organization: CodeSourcery
To: law@redhat.com, Tom Crick <cs1tc@bath.ac.uk>
Subject: Re: Building GENERIC trees
Date: Fri, 05 Mar 2004 18:23:00 -0000
User-Agent: KMail/1.5.4
Cc: gcc@gcc.gnu.org
References: <200403051811.i25IB8d0021219@speedy.slc.redhat.com>
In-Reply-To: <200403051811.i25IB8d0021219@speedy.slc.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200403051823.13994.paul@codesourcery.com>
X-SW-Source: 2004-03/txt/msg00339.txt.bz2

> The f95 front-end generates GENERIC trees directly and may be useful for
> you to use as a reference.

Not really. The f95 frontend does generate its own trees. It then translates 
them into GENERIC trees a function at a time as a seperate pass.

I agree that this is probably easier than building GENERIC+language extensions 
and lowering with genericise(). This is especially true if your language 
isn't very close to C.

Paul