From owner-freebsd-questions Sat Oct 31 15:59:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05437 for freebsd-questions-outgoing; Sat, 31 Oct 1998 15:59:39 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dt053n18.san.rr.com (dt053n18.san.rr.com [204.210.34.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05426 for ; Sat, 31 Oct 1998 15:59:27 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053n18.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA15383; Sat, 31 Oct 1998 15:59:21 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <363BA458.604FFB30@gorean.org> Date: Sat, 31 Oct 1998 15:59:20 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1026 i386) X-Accept-Language: en MIME-Version: 1.0 To: "questions@FreeBSD.ORG" CC: Dan Nelson Subject: Re: Cyrix 6x86 CPU References: <199810311552.KAA14228@laker.net> <19981031141836.B2302@emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Nelson wrote: > So for all but the most rabid performace freaks that can sense when a > branch is predicted wrong or when a pipeline stalls, including all > possible CPU types will make absolutely no difference. So if we know how to conditionalize this code, why is it still necessary to specify the cpu type? Why not have /usr/sbin/config detect the cpu type and DTRT? (Or whatever convenient/efficient mechanism is appropriate.) Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message