From owner-freebsd-hackers Tue Jun 20 06:53:41 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA21089 for hackers-outgoing; Tue, 20 Jun 1995 06:53:41 -0700 Received: from lambda.demon.co.uk (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA21081 ; Tue, 20 Jun 1995 06:53:35 -0700 Received: (from paul@localhost) by lambda.demon.co.uk (8.6.11/8.6.9) id OAA04776; Tue, 20 Jun 1995 14:53:34 +0100 From: Paul Richards Message-Id: <199506201353.OAA04776@lambda.demon.co.uk> Subject: Re: Just FYI, gcc 2.7.0 is out, do we plan to switch to it? To: gibbs@freefall.cdrom.com (Justin T. Gibbs) Date: Tue, 20 Jun 1995 14:52:58 +0100 (BST) Cc: bde@zeta.org.au, phk@freefall.cdrom.com, ache@astral.msk.su, hackers@freebsd.org In-Reply-To: <199506181758.KAA23441@freefall.cdrom.com> from "Justin T. Gibbs" at Jun 18, 95 10:58:57 am Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1481 Sender: hackers-owner@freebsd.org Precedence: bulk In reply to Justin T. Gibbs who said > > >>> I think we should put it into 2.2 immediately (or maybe wait for 2.7.1). > >>> > >>2.7.0 -- no way. > >>2.7.1 -- maybe > >>2.7.2 -- probably. > > > >I want to get correct support for freebsd in it (it still has a 1.x > >freebsd.h with the most inappropriate parts `#if 0'ed...). 2.7.1 may > >be too late to start. 2.7.0 may be too late to start. > > > >Bruce > > I second Bruce on this. We have a "stable" branch now, so there is > no harm in bringing a new gcc in now on the 2.2 branch. The sooner > we know about the problems in the 2.7 series, the sooner we can work > to get them fixed and report them back to the FSF. I'm keen to upgrade sooner rather than later, 2.2 is a fair way off, we have time to shake out a compiler upgrade. The problem of course is that you might be banging your head against the wall thinking why your latest change is broken and it turns out the compiler is causing it. We need a way to run the old compiler in these situations to eliminate the new compiler from the equation. I alos think gcc should be ported to BSD from scratch so it's ready for multi-arch and placed properly on a vendor branch. Any FreeBSD specific fixes currently in our cvs tree need to be pulled out and passed back to the FSF. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)