From owner-cvs-src@FreeBSD.ORG Thu Mar 18 09:28:30 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A2E816A4CE; Thu, 18 Mar 2004 09:28:30 -0800 (PST) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2795043D31; Thu, 18 Mar 2004 09:28:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.10) with ESMTP id i2IHSTTu042641; Thu, 18 Mar 2004 09:28:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i2IHSRsM042640; Thu, 18 Mar 2004 09:28:27 -0800 (PST) (envelope-from obrien) Date: Thu, 18 Mar 2004 09:28:27 -0800 From: "David O'Brien" To: Alexander Leidinger Message-ID: <20040318172827.GB41559@dragon.nuxi.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040318162358.3f57aef3@Magellan.Leidinger.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Tom Rhodes cc: src-committers@freebsd.org cc: cvs-all@freebsd.org cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/share/mk bsd.cpu.mk bsd.dep.mk bsd.lib.mk bsd.sys.mk src/sys/conf files kern.mk kern.pre.mk kmod.mk src/sys/dev/aic7xxx/aicasm Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 17:28:30 -0000 On Thu, Mar 18, 2004 at 04:23:58PM +0100, Alexander Leidinger wrote: > It seems Intel identified some issues regarding icc when used on AMD > processors. Yah, the issue of loosing sales to a better technology. The issues aren't technical at all. > I don't know if there is malicious intend to use some > specific instructions or not. I don't know if there exist instructions > which perform the same action with the same efficiency (I don't define > what "efficient" means in this case) without resulting in a segfault on > AMD processors. AMD CPU's are bug-for-bug compatible with Intel's -- they *have* to be. AMD has multiple huge software compatibility and verification labs to ensure COTS products depending on weird Intel bugs will work on AMD processors. > Intel at least seems to be > aware of some issues and protects the user from misbehavior. The test > may be not strict enough in some cases, and maybe too strict in other > cases, but as long as you can't proof they do this with malicious > intend, you should try to calm down. Why do they do a CPUID check and look for "GenuineIntel" vs. looking at the feature bits "SSE,SSE2"?? Intel's compilers only started acting this way after AMD announced the Opteron and it was clear that large enterprise ISV's (who are the users of the Intel compilers) would start certifying an AMD platform. Just to be clear -- I'm not against supporting a 2nd compiler in /usr/src at all. Just don't think Intel is the most gracious compiler vendor. I'll also strongly push back on ever using 'icc' as part of the release build. -- -- David (obrien@FreeBSD.org)