From owner-freebsd-current Wed May 27 18:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22227 for freebsd-current-outgoing; Wed, 27 May 1998 18:05:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22128 for ; Wed, 27 May 1998 18:05:15 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA19466; Thu, 28 May 1998 01:05:06 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA09180; Thu, 28 May 1998 03:04:59 +0200 (MET DST) Message-ID: <19980528030458.00490@follo.net> Date: Thu, 28 May 1998 03:04:58 +0200 From: Eivind Eklund To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) References: <19980527225647.36082@follo.net> <199805280034.CAA17560@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805280034.CAA17560@ceia.nordier.com>; from Robert Nordier on Thu, May 28, 1998 at 02:34:36AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 02:34:36AM +0200, Robert Nordier wrote: > Eivind Eklund wrote: > > Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > > inertia) in using this as our main compiler: The use of asm() for some > > macros in the kernel, and the use of linker sets. What do you think > > our chance of working around these are? > > I think we can find reasonable ways over the technical hurdles. > Possibly, though, we need to commit to supporting TenDRA as a secondary > compiler initially, with a change 6-12 months down the line, if things > work out. We have to support it for a while before switching, at least. The first step is getting the entire tree to build. > >From a few tests here, it is starting to look as though the trans386 > optimization needs additional work. I know that some of the code I > haved looked at was highly-optimized, so the slow times may be fairly > readily correctable. What kind of optimizations are you missing? I think there might be additional ANDF->ANDF optimizations we might be able to grab hold of from the old OSF projects; they're marked as 'freely available'. If what you're missing is high-level optimizations, this might be a good way to go. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message