From owner-freebsd-sparc64@FreeBSD.ORG Sat Aug 9 17:20:28 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB66337B401 for ; Sat, 9 Aug 2003 17:20:28 -0700 (PDT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBCD743F75 for ; Sat, 9 Aug 2003 17:20:27 -0700 (PDT) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id 1711D8B for ; Sat, 9 Aug 2003 18:20:27 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h7A0KQU22209 for sparc64@freebsd.org; Sat, 9 Aug 2003 18:20:26 -0600 Date: Sat, 9 Aug 2003 18:20:26 -0600 From: Tillman To: sparc64@freebsd.org Message-ID: <20030809182026.W16062@seekingfire.com> References: <20030807062536.GA68747@dragon.nuxi.com> <20030809084019.GA4704@rot13.obsecurity.org> <20030809235533.GA56513@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030809235533.GA56513@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Aug 09, 2003 at 04:55:33PM -0700 X-Urban-Legend: There is lots of hidden information in headers Subject: Re: ponderous 'make world' times post GCC 3.3... X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2003 00:20:29 -0000 On Sat, Aug 09, 2003 at 04:55:33PM -0700, David O'Brien wrote: > On Sat, Aug 09, 2003 at 01:40:19AM -0700, Kris Kennaway wrote: > > This suggests that something might have been pessimized with the gcc > > 3.3 code generation on sparc. i.e. when gcc 3.3 is built with gcc 3.2 > > (your build 2, which used the installed 3.2 compiler to build the 3.3 > > compiler that was then used for the remainder of the world build), it > > performs well (your build 2), but when gcc 3.3 is built with gcc 3.3 > > it performs slowly. > > > > I wonder if the gcc 3.3 compiler specs were set up incorrectly for > > sparc. > > I can think of nothing in the sparc MD compiler specs that could account > for this. Mostly things there are in the "work / doesn't work" category. Is there some kind of profiling that I could perform during a buildworld that might be helpful? -T -- Humans hardly ever learn from the experience of others. They learn - when they do, which isn't often - on their own, the hard way. - Robert Heinlein