From owner-freebsd-current Fri Sep 4 00:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14335 for freebsd-current-outgoing; Fri, 4 Sep 1998 00:18:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14330 for ; Fri, 4 Sep 1998 00:18:23 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA11929; Fri, 4 Sep 1998 08:17:44 +0100 (BST) Date: Fri, 4 Sep 1998 08:17:44 +0100 (BST) From: Doug Rabson To: John Birrell cc: current@FreeBSD.ORG Subject: Re: Compiler problems with gcc-2.7.2.1 In-Reply-To: <199809032336.JAA04070@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Sep 1998, John Birrell wrote: > Doug Rabson wrote: > > I have been having occaisonal problems with gcc-2.7.2.1 on the alpha where > > it makes bad register allocation choices, leading to broken code. I don't > > think anything in our build tickles this bug but XFree86 certainly does. > > Does this occur without optimization? It only happens with optimisation. > > > I tracked down a set of patches from RedHat 5.0 which fix the problem but > > they are for gcc-2.7.2.3. I am not sure how to go about committing this. > > I have patched my tree up to 2.7.2.3 and added the RedHat patches but it > > really needs someone (hopefully not me) to do a proper import of 2.7.2.3. > > What are our options here wrt Alpha _and_ i386? > > If we stick with what we have for 3.0 to avoid a last minute change that > might destabilize the i386 release, we need to at least release a snapshot > of FreeBSD/Alpha at the same time and that must contain the tools to > support building the world. The alpha Alpha 8-) release can contain > XFree86 libs and clients built on a later compiler if required, since we > don't build those with the world That might be ok given that we are not going to call the Alpha bits a release. > > I'd like to see the compiler issue reviewed after 3.0 in the light of > the release of egcs and the poor C++ support that gcc 2.7.X has. It would be a good idea to upgrade to a modern compiler after the release. I suspect that gcc-2.8.x will be more acceptable for most people. The C++ support is roughly the same in gcc-2.8.x and egcs-1.x afaik. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message