From owner-cvs-all@FreeBSD.ORG Thu Mar 18 12:16:49 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F53216A4D0 for ; Thu, 18 Mar 2004 12:16:49 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 5B4EA43D1F for ; Thu, 18 Mar 2004 12:16:49 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 55974 invoked by uid 1002); 18 Mar 2004 20:16:49 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 18 Mar 2004 20:16:49 -0000 Message-ID: <405A02DE.7000402@freebsd.org> Date: Thu, 18 Mar 2004 13:13:18 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Rhodes References: <200403122136.i2CLaCm9096276@repoman.freebsd.org> <20040315033213.GA40858@dragon.nuxi.com> <20040315180324.0fa39609@Magellan.Leidinger.net> <20040318002208.GC2541@dragon.nuxi.com> <20040318162358.3f57aef3@Magellan.Leidinger.net> <20040318172827.GB41559@dragon.nuxi.com> <20040318131238.12142bf1@localhost> <20040318145507.7acb75fc@localhost> In-Reply-To: <20040318145507.7acb75fc@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: src-committers@freebsd.org cc: cvs-src@freebsd.org cc: cvs-all@freebsd.org cc: obrien@freebsd.org cc: Alexander Leidinger cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: cvs commit: src/share/mk bsd.cpu.mk bsd.dep.mk bsd.lib.mkbsd.sys.mksrc/sys/dev/aic7xxx/aicasm Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 20:16:49 -0000 Tom Rhodes wrote: > On Thu, 18 Mar 2004 20:27:20 +0100 > des@des.no (Dag-Erling Smørgrav) wrote: > > >>Tom Rhodes writes: >> >>>"David O'Brien" wrote: >>> >>>>I'll also strongly push back on ever using 'icc' as part of the release >>>>build. >>> >>>push back a release build. Are you worried that the 'rumors?' of >>>better, more optimized binaries going to hurt the AMD effort? >> >>No, he's rightfully worried that we might end up with a release that >>doesn't run on AMD hardware. And you're trolling. > > > I can understand that, DES, David. I just wanted to gather more > information. Sorry if I seemed like a troll, that wasn't my intent. > Ok, let's hear from the release guys. Oh, that's me! First of all, while the project has a license to run icc on a cluster computer and release the outputed binaries, does that mean that the project can distribute icc in the base system, or on one of the release cd's? My understanding is 'no'. So let's say that I hack up the release makefiles so that they use icc, and produce an icc-optimized release. What's the first thing that many people do right after they install their system? They compile a new kernel. Since icc isn't available to them when they do this, they've lost the benefit of what was distributed on the CD. Now this all assumes that release CD's are built on cluster machines. In fact, none of them are for any architecture. I, and the others who build the other arches, usually build them on local hardware so that we can QA the results before uploading them to ftp-master. So unless we all get icc licenses for our local machines, using it isn't going to happen. Also, I don't know if David's concerns about icc having different behaviour on Intel vs AMD chips are true, but I generally trust him on these matters since it's his job (both real job and project job) to know. It's also within the realm of possibilities for Intel. So this is yet another strike against using it in a release. I think I mentioned this before, but a nice compromise would be to put a set of icc-compiled binaries in an obvious location on the ftp and web sites, and encourage people to try them on their already-installed systems. Maybe someday we could even have enough computing horsepower to do on-demand kernel compiles for people. Scott