From owner-freebsd-questions@FreeBSD.ORG Wed Jan 31 12:56:03 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 533C016A401 for ; Wed, 31 Jan 2007 12:56:03 +0000 (UTC) (envelope-from salkillen@internode.on.net) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id CFDDF13C46B for ; Wed, 31 Jan 2007 12:56:02 +0000 (UTC) (envelope-from salkillen@internode.on.net) Received: from ppp201-69.static.internode.on.net (HELO idonz003.idonz.net) ([150.101.201.69]) by ipmail01.adl2.internode.on.net with ESMTP; 31 Jan 2007 23:10:43 +1030 X-IronPort-AV: i="4.13,262,1167571800"; d="scan'208"; a="81828271:sNHT21247597" From: Scott Killen Organization: na To: freebsd-questions@freebsd.org Date: Wed, 31 Jan 2007 23:40:38 +1100 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701312340.38593.salkillen@internode.on.net> Subject: gcc compiler cputype, prescott or nocona confusion X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 12:56:03 -0000 Hi, When recompiling the world or kernel in FreeBSD i386 Rel 6.1 with, "# make buildworld" or "# make buildkernel KERNCONF=MYSMPCONF" (or building anything anything else for that matter), even though I have "CPUTYPE?=nocona" set in my "/etc/make.conf" file the compiler seems to head back to a default of "-march=prescott" when compiling many of the functions on a Dual Xeon 3.6g (nocona) machine! This doesn't happen when compiling for other machine types, I've tried it on a Dual PentiumPro, Dual PII, Dual PIII setting the CPUTYPE to the correct cpu type and the -march sticks to the assigned cpu type through all operations and produces nice quick optimized code. Why is this so? Is it because the "nocona" machine type optimization refers to the EMT64 technology and thus is rejected when compiling for i386 targets rather than amd64 or emt64 targets and Gcc rejects it? Regards Scott K