From owner-freebsd-current@FreeBSD.ORG Thu Dec 14 18:42:07 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E47216A65A for ; Thu, 14 Dec 2006 18:42:07 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 857944425E for ; Thu, 14 Dec 2006 18:29:03 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c58-107-94-118.belrs4.nsw.optusnet.com.au [58.107.94.118]) by mail06.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id kBEIUQMj008037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Dec 2006 05:30:27 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id kBEIUQSG003224 for ; Fri, 15 Dec 2006 05:30:26 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id kBEIUQ04003223 for freebsd-current@freebsd.org; Fri, 15 Dec 2006 05:30:26 +1100 (EST) (envelope-from peter) Date: Fri, 15 Dec 2006 05:30:26 +1100 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20061214183026.GA1532@turion.vk2pj.dyndns.org> References: <20061213192150.CF83D16A417@hub.freebsd.org> <200612131711.50921.mi+mx@aldan.algebra.com> <4580DFAB.3080601@FreeBSD.org> <200612140917.25523@aldan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: Let's use gcc-4.2, not 4.1 -- OpenMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 14 Dec 2006 18:42:07 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 2006-Dec-14 16:35:41 +0100, Ivan Voras wrote: >For what it's worth: +1. It's going to be practically required even for >medium-performance applications as CPU clock rate stagnate and more >cores are grown. Sun have stated that they do not expect SPARC clock speeds to increase significantly. Instead, they will be doubling the number of threads per chip every year or so. (32 now, 64 next year). Intel have announced quad-core x86 chips. AMD will presumably follow suit. Based on the current release engineering guidelines, FreeBSD 7.x will probably be supported until around 2011 (-RELEASE next year, -STABLE for about 18 months, continued support for 2 years after 8-RELEASE). The system toolchain is a critical piece of infrastructure and making a major change within a release is impractical. IMHO, rather than looking at what is mature now, FreeBSD -CURRENT should be looking at a toolchain that is closer to the leading edge (as long as there are no significant regressions in stability) but will mature shortly before 7-RELEASE. This maximises the period of "vendor" support for the toolchain and therefore reduces the amount of FreeBSD developer effort that will be spent supporting the toolchain once the vendor stops doing so. The computing industry moves relatively fast and you can't wait for your supplier's product to be fully mature before you start developing on it or your customers will go elsewhere because their customers won't buy what they see as a product running on an obsolete base. --=20 Peter Jeremy --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFgZhC/opHv/APuIcRAnQkAKDBajjY/x7mf3da9gAa7cGYqb8VSwCfe/b0 dQDOgfQUHBsuYIOV7xvUKs4= =mTM+ -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--