From owner-freebsd-current  Wed Aug  7 23:02:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA12945
          for current-outgoing; Wed, 7 Aug 1996 23:02:35 -0700 (PDT)
Received: from parkplace.cet.co.jp ([202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA08646
          for <current@freebsd.org>; Wed, 7 Aug 1996 22:28:28 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id FAA11968; Thu, 8 Aug 1996 05:27:52 GMT
Date: Thu, 8 Aug 1996 14:27:51 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: "Brian N. Handy" <handy@sag.space.lockheed.com>
cc: Nate Williams <nate@mt.sri.com>, current@freebsd.org
Subject: Re: Whither gcc 2.7? 
In-Reply-To: <Pine.OSF.3.94.960807111555.5199U-100000@sag.space.lockheed.com>
Message-ID: <Pine.SV4.3.93.960808142325.11801C-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 7 Aug 1996, Brian N. Handy wrote:

> I guess another thing I wonder about...has anyone thought about the future
> plans of tracking gcc?  We've been running 2.6.3 for a loong time, are we
> going to move to 2.7.# and stay with it or is FreeBSD going to start
> tracking gcc more closely? 

Since we're using gcc to compile the kernel we need to identify stable
releases of gcc and stick with it for a while.

Closely tracking and incorporating all gcc releases (including unstable
releases) is not a high priority. 

Regards,


Mike Hancock