From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22245 invoked by alias); 6 Mar 2003 18:08:09 -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 22102 invoked from network); 6 Mar 2003 18:07:56 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by 172.16.49.205 with SMTP; 6 Mar 2003 18:07:56 -0000 Received: by fw-cam.cambridge.arm.com; id SAA21587; Thu, 6 Mar 2003 18:07:55 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma021081; Thu, 6 Mar 03 18:07:01 GMT Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id SAA20045; Thu, 6 Mar 2003 18:06:59 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h26I6xY18183; Thu, 6 Mar 2003 18:06:59 GMT Message-Id: <200303061806.h26I6xY18183@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: Joern Rennecke cc: Richard Earnshaw , Olivier Galibert , Gabriel Dos Reis , Rupert Wood , gcc@gcc.gnu.org Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: Re: Putting C++ code into gcc front end In-reply-to: Your message of "Thu, 06 Mar 2003 16:47:04 GMT." <3E677B88.AAA35F5C@superh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Mar 2003 18:25:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-03/txt/msg00438.txt.bz2 > > > > 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 (or are > > you proposing to maintain it in perpetuity?) > > Well, for new hosts, we can use a cross-compiler on an established host to > start the bootstrapping. > That way, we need no pre-existing compiler on the new system. *IF* you don't need proprietary tools on the target to produce your image. R.