From owner-freebsd-current@FreeBSD.ORG Tue Apr 26 10:38:06 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 B5D6416A4CE for ; Tue, 26 Apr 2005 10:38:06 +0000 (GMT) Received: from hex.athame.co.uk (guru164.netsonic.fi [194.29.193.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 454C343D4C for ; Tue, 26 Apr 2005 10:38:06 +0000 (GMT) (envelope-from andy@athame.co.uk) Received: from hex.int.athame.co.uk ([192.168.1.1] helo=localhost) by hex.athame.co.uk with esmtp (Exim 4.50 (FreeBSD)) id 1DQNS8-0003jo-KQ for freebsd-current@freebsd.org; Tue, 26 Apr 2005 13:38:04 +0300 From: Andy Fawcett To: freebsd-current@freebsd.org Date: Tue, 26 Apr 2005 13:37:59 +0300 User-Agent: KMail/1.8 References: <20050425010242.GA44110@xor.obsecurity.org> <20050425182033.GC40370@xor.obsecurity.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504261338.01026.andy@athame.co.uk> Subject: Re: GCC 4.0 [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: Tue, 26 Apr 2005 10:38:06 -0000 On Monday 25 April 2005 23:28, Garance A Drosihn wrote: > For what it's worth: Some friends of mine are claiming that "Tiger" > (MacOS 10.4) will be coming with gcc 4.0. And Tiger is already > shipping, although the official release date isn't until this Friday. > > I'm not saying that we should switch to it because of that, but I'm > just mentioning it as an interesting data point (assuming it is true!). FYI, the KDE project just blacklisted gcc 4.0.0, because "it is known to miscompile KDE. Please use a newer version, or if that is not yet available, choose an older version." No, I don't know what the exact problems are, but they are obviously severe enough for KDE to say "no thanks" to 4.0.0. A.