From owner-freebsd-hackers  Sun Jun 18 11:06:41 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA24110
          for hackers-outgoing; Sun, 18 Jun 1995 11:06:41 -0700
Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA24104
          ; Sun, 18 Jun 1995 11:06:39 -0700
Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA02058; Sun, 18 Jun 1995 11:06:52 -0700
From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Message-Id: <199506181806.LAA02058@gndrsh.aac.dev.com>
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: Sun, 18 Jun 1995 11:06:51 -0700 (PDT)
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
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1087      
Sender: hackers-owner@freebsd.org
Precedence: bulk

> 
> >>> 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.

And I third this, the 2.2 release branch is not due for release rolling
for at least 3 months *NOW* is the time to start playing with a new compiler,
not 2 months from now when it would be getting close to branch again.

The only way to get a new gcc tested out is to get the masses using it.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD