From owner-freebsd-questions Mon Sep 2 4: 2: 1 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A462137B400 for ; Mon, 2 Sep 2002 04:01:57 -0700 (PDT) Received: from web20305.mail.yahoo.com (web20305.mail.yahoo.com [216.136.226.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 6098F43E3B for ; Mon, 2 Sep 2002 04:01:57 -0700 (PDT) (envelope-from magudexter@yahoo.com) Message-ID: <20020902110157.51962.qmail@web20305.mail.yahoo.com> Received: from [212.93.128.97] by web20305.mail.yahoo.com via HTTP; Mon, 02 Sep 2002 04:01:57 PDT Date: Mon, 2 Sep 2002 04:01:57 -0700 (PDT) From: magudexter Subject: k6 or i686 optimization on AMD Athlon? To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! Every time I build a source I want to specify the proper compiler parameters in order to max out the performance. This is the case with make world. I recently purchase a AMD XP processor belonging to the k7 family. Even though the /etc/default/make.conf mentions the k7 processor in CPUTYPE the cc compiler know only k6 and i686(alias pentiumpro). Every build using the make.conf with the CPUTYPE=k7 make actually a build with march=k6(which belongs to i586 family). I am not aware of the internals of these processors but wouldn't it be wise to use i686 to the AMD Duron/Athlon/TB/XP processors to gain more performance then the k6 build? P.S. And one more question - does FreeBSD supports the non-exec stack available on the i386 family (*any* detail on these is appreciated)? Thanks, Costin __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message