From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8147 invoked by alias); 4 Mar 2003 21:52:31 -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 8126 invoked from network); 4 Mar 2003 21:52:30 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by 172.16.49.205 with SMTP; 4 Mar 2003 21:52:30 -0000 Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h24LoFH2029166; Tue, 4 Mar 2003 22:50:15 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h24LoElO029165; Tue, 4 Mar 2003 22:50:14 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Benjamin Kosnik Cc: gcc@gcc.gnu.org Subject: Re: Putting C++ code into gcc front end References: <20030304114033.180e04b6.bkoz@redhat.com> From: Gabriel Dos Reis In-Reply-To: <20030304114033.180e04b6.bkoz@redhat.com> Organization: Integrable Solutions Date: Tue, 04 Mar 2003 22:02:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg00280.txt.bz2 Benjamin Kosnik writes: | > what if we only built the C front end, optimizers, and back end during | > all three stages of a bootstrap? And then came back to build the other | > front ends when we were done? | | I think this sounds like a really good idea. Seconded. -- Gaby