From owner-freebsd-current@FreeBSD.ORG Mon Apr 25 14:52:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA0D016A4CE; Mon, 25 Apr 2005 14:52:18 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E58043D54; Mon, 25 Apr 2005 14:52:18 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.50 (FreeBSD)) id 1DQ4wQ-0006fk-FW; Mon, 25 Apr 2005 16:52:06 +0200 Date: Mon, 25 Apr 2005 16:52:06 +0200 From: Kirill Ponomarew To: Scott Long Message-ID: <20050425145206.GM91852@voodoo.oberon.net> References: <6.2.1.2.0.20050424204611.072105a0@64.7.153.2> <20050425010242.GA44110@xor.obsecurity.org> <6.2.1.2.0.20050424210422.03d22990@64.7.153.2> <20050425014453.GA59981@xor.obsecurity.org> <426C6B1D.3040704@elischer.org> <20050425061459.GA33247@xor.obsecurity.org> <20050425062106.GB91852@voodoo.oberon.net> <426CF3DE.4000409@samsco.org> <20050425144108.GK91852@voodoo.oberon.net> <426D0252.5050805@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <426D0252.5050805@samsco.org> X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE Keywords: 579279786 cc: current@freebsd.org cc: Kris Kennaway cc: freebsd-current@freebsd.org cc: Julian Elischer cc: Mike Tancsa Subject: Re: FreeBSD 6 is coming too fast X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2005 14:52:19 -0000 On Mon, Apr 25, 2005 at 08:44:34AM -0600, Scott Long wrote: > >No, I'm not going to do it because of lack of knowledge, there are > >people who have more experience with it than me. > > > Well, as I said in another email, switching to GCC 4 just because of > dubious "25% faster" (faster at what? compiling? resulting generated > code? crashing?) claims in the changelog is not a terribly good > reason =-) 25% faster to compile the code, not running it. > It seems that every time GCC claims to get "faster", our > buildworld times increase by 10%. Maybe the generated code is > better and faster, but it's no secret that gcc spends a lot more > CPU cycles on code genreation and optimization than it did in the > 2.x series. Note also that the GCC 4.0 changelog mentions that > the -O0 flag is faster; that's wonderful, but has no practical > value to real people. -Kirill