From owner-freebsd-hackers Fri Apr 10 16:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03604 for freebsd-hackers-outgoing; Fri, 10 Apr 1998 16:00:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bookcase.com (root@notes.bookcase.com [207.22.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03569 for ; Fri, 10 Apr 1998 16:00:07 -0700 (PDT) (envelope-from chadf@bookcase.com) Received: from localhost (chadf@localhost) by bookcase.com (8.8.8/8.8.8) with SMTP id SAA02915 for ; Fri, 10 Apr 1998 18:59:22 -0400 (EDT) (envelope-from chadf@bookcase.com) Date: Fri, 10 Apr 1998 18:59:22 -0400 (EDT) From: "Chad M. Fraleigh" X-Sender: chadf@notes To: freebsd-hackers@FreeBSD.ORG Subject: Re: bcopy implementation In-Reply-To: <199804031420.QAA05837@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Apr 1998, Mikael Karpberg wrote: > According to Dave Marquardt: > Well, if you want everything to go faster, you optimize for the hardware > you're actually gonna run on. Now, it would be quite possible too add > ifdefs so that you would add -DOPTIMIZE_FOR_PENTIUM to CFLAGS in make.conf > and then make world. And libc would be compiled with that optimization, etc. If you were only to do this for the shared libc, and not the static one it should be rather safe. That way someone can't statically link a binary, then copy it to another non-Pentium FreeBSD system without realizing the mistake. Is there a define set to differenciate when doing shared vs static lib compiles? (I would assume there is, but I've never looked). -Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message