This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Putting C++ code into gcc front end

From: Geoff Keating <geoffk at geoffk dot org>
To: Phil Edwards <phil at jaj dot com>
Cc: Richard dot Earnshaw at arm dot com, Olivier Galibert <galibert at pobox dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, Rupert Wood <me at rupey dot net>, gcc at gcc dot gnu dot org
Date: 04 Mar 2003 12:49:31 -0800
Subject: Re: Putting C++ code into gcc front end
References: <200303041445.h24Ejhb15458@pc960.cambridge.arm.com><87ptp711nj.fsf@egil.codesourcery.com><20030304174003.GA15255@disaster.jaj.com>

Phil Edwards <phil at jaj dot com> writes:

> On Tue, Mar 04, 2003 at 09:29:04AM -0800, Zack Weinberg wrote:
> > Ignoring Ada for the moment, 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've always been confused why the C++ frontend was rebuilt multiple times
> during a bootstrap; actually assumed that it was done for some kind of odd
> binutils compatability or hysterical raisins.  Please, if this is possible,
> let's do it.  Bootstrap times will go down as a nice side-effect.

It's a test of the C compiler.  It verifies that the un-optimised C
compiler generates the same code as the optimised C compiler.

-- 
- Geoffrey Keating <geoffk at geoffk dot org>

Follow-Ups:
- Re: Putting C++ code into gcc front end
  - From: Gabriel Dos Reis

References:
- Re: Putting C++ code into gcc front end
  - From: Richard Earnshaw
- Re: Putting C++ code into gcc front end
  - From: Zack Weinberg
- Re: Putting C++ code into gcc front end
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]