From owner-freebsd-current Thu Sep 3 16:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16058 for freebsd-current-outgoing; Thu, 3 Sep 1998 16:24:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16051 for ; Thu, 3 Sep 1998 16:24:23 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id JAA04070; Fri, 4 Sep 1998 09:36:32 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809032336.JAA04070@cimlogic.com.au> Subject: Re: Compiler problems with gcc-2.7.2.1 In-Reply-To: from Doug Rabson at "Sep 3, 98 11:42:37 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Fri, 4 Sep 1998 09:36:32 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? > 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. 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. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message