From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1702 invoked by alias); 4 Mar 2003 14:55:42 -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 1695 invoked from network); 4 Mar 2003 14:55:41 -0000 Received: from unknown (HELO uniton.integrable-solutions.net) (62.212.99.186) by 172.16.49.205 with SMTP; 4 Mar 2003 14:55:41 -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 h24EqwH2027187; Tue, 4 Mar 2003 15:52:58 +0100 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.3/8.12.3/Submit) id h24EqvSQ027186; Tue, 4 Mar 2003 15:52:57 +0100 X-Authentication-Warning: uniton.integrable-solutions.net: gdr set sender to gdr@integrable-solutions.net using -f To: Richard.Earnshaw@arm.com Cc: Olivier Galibert , Rupert Wood , gcc@gcc.gnu.org Subject: Re: Putting C++ code into gcc front end References: <200303041445.h24Ejhb15458@pc960.cambridge.arm.com> From: Gabriel Dos Reis In-Reply-To: <200303041445.h24Ejhb15458@pc960.cambridge.arm.com> Organization: Integrable Solutions Date: Tue, 04 Mar 2003 15:03:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg00200.txt.bz2 Richard Earnshaw writes: | > > Just at this point it isn't reasonable to assume that there | > > are conforming (even sufficiently conforming) C++ compilers widely | > > available on the wide range of hosts that GCC currently supports. | > | > There is gcc 3.2.2. | | But that doesn't support hosts that might come along in the future Right. On this issue, in my opinion, we should proceed in steps. I believe R.'s approach is a fair first step. Let's make the C++ front-end compilable by ISO C90 compilers. Then we'll tackle the next issue in due time. -- Gaby