From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 20 21:35:04 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9746716A4CE for ; Sat, 20 Nov 2004 21:35:04 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C14943D1F for ; Sat, 20 Nov 2004 21:35:04 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 552BE2A8D5 for ; Sat, 20 Nov 2004 13:35:04 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id D2F15E2B3 for ; Sat, 20 Nov 2004 13:35:03 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iAKLZ3tm079614; Sat, 20 Nov 2004 13:35:03 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAKLZ3cK079613; Sat, 20 Nov 2004 13:35:03 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org, Gert Cuykens Date: Sat, 20 Nov 2004 13:35:02 -0800 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411201335.02738.peter@wemm.org> Subject: Re: cputype FX-53 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 21:35:04 -0000 On Friday 19 November 2004 11:14 pm, Gert Cuykens wrote: > Hi whats the cputype of a FX-53 please You don't need to set CPUTYPE yet. If you really want to, you could use any of "k8", "opteron" or "athlon64". The "k8" label is probably what you should use, if you really want to set something since that is the fundamental cpu core type that is shared across all the athlon64/opteron family at this point in time. There will be a k9 and k10 core at some point and it is probably safe to assume that they'll be different enough in features or optimizer strategies to merit a new gcc optimizer target. For 64 bit intel cpus, you can use "nocona". At some point, not setting CPUTYPE will target the lowest common features of both cpus, eg: no SSE3, no 3dnow, etc. But for now, gcc doesn't use sse3 or 3dnow with the default settings. There is a small optimizer benefit to setting CPUTYPE="nocona" for intel cpus though. It causes the gcc optimizer to use the pentium4 insanely-long-pipeline optimizer strategies instead of something suitable for the AMD cpus. It also seems to cause gcc to make extra effort to avoid partial register pipeline stalls. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5