From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 568 invoked by alias); 25 Mar 2003 19:54:14 -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 551 invoked from network); 25 Mar 2003 19:54:13 -0000 Received: from unknown (HELO mail.cs.umn.edu) (128.101.32.202) by sources.redhat.com with SMTP; 25 Mar 2003 19:54:13 -0000 Received: from bose.cs.umn.edu (bose.cs.umn.edu [128.101.35.195]) by mail.cs.umn.edu (Postfix) with ESMTP id ECD7611408; Tue, 25 Mar 2003 13:54:12 -0600 (CST) Received: by bose.cs.umn.edu (Postfix, from userid 818) id 66C05326F; Tue, 25 Mar 2003 13:54:12 -0600 (CST) To: "Kaveh R. Ghazi" Cc: mark@codesourcery.com, gcc@gcc.gnu.org, gdr@integrable-solutions.net Subject: Re: Converting to ISO C89 From: Raja R Harinath Date: Tue, 25 Mar 2003 20:38:00 -0000 In-Reply-To: <200303251752.MAA08671@caip.rutgers.edu> ("Kaveh R. Ghazi"'s message of "Tue, 25 Mar 2003 12:52:23 -0500 (EST)") Message-ID: User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.3.50 (gnu/linux) References: <200303250642.h2P6gZ4r025932@doubledemon.codesourcery.com> <1048612019.25895.7.camel@doubledemon.codesourcery.com> <200303251752.MAA08671@caip.rutgers.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg01562.txt.bz2 Hi, "Kaveh R. Ghazi" writes: > > > Great! > > > > > > Is the topic on using C++ in the Java front-end handled by the SC? > > > > If necessary, the SC could deal with this. > > > > But it would be much better if there were consensus here first. > > > > I think the topic of using C++ in gcj is different: it doesn't affect > > the end-user. Using C89 in GCC means that the user must start with a > > C89 compiler; using C++ in gcj doesn't affect the set of tools the > > user must have at all. So, I think it's more a technical decision > > than an SC decison. > > Agreed. > > IMHO once we've decided to require ISO C89 to bootstrap, we should > remove gcc-isms from the cp/ dir and compile cc1plus during stage1. > We can perhaps condition cc1plus during stage1 iff java is enabled. Hopefully the ISO C89 changes also make the source C++-safe. In which case, eventually there should be some way of running a stage2 bootstrap with that 'cc1plus' in addition to 'cc1'. Running that occasionally and comparing it with 'cc1' would ensure more uniformity. - Hari -- Raja R Harinath ------------------------------ harinath@cs.umn.edu