From owner-freebsd-current Sat Sep 16 22:23:56 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
by hub.freebsd.org (Postfix) with ESMTP
id A180137B424; Sat, 16 Sep 2000 22:23:53 -0700 (PDT)
Received: from localhost (kris@localhost)
by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA20741;
Sat, 16 Sep 2000 22:23:53 -0700 (PDT)
(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Sat, 16 Sep 2000 22:23:53 -0700 (PDT)
From: Kris Kennaway <kris@FreeBSD.org>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: FreeBSD Current <freebsd-current@FreeBSD.org>
Subject: Re: upgrade libgmp?
In-Reply-To: <200009170506.WAA07848@troutmask.apl.washington.edu>
Message-ID: <Pine.BSF.4.21.0009162221180.20280-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Sat, 16 Sep 2000, Steve Kargl wrote:
> I need to review the gmp documents again, but I not sure
> the preference order is much of an issue. By default,
> CPU_TYPE="generic" would build the C code, which should work
> on all architectures supported by FreeBSD. If a user explicitly
> sets CPU_TYPE in /etc/make.conf, then the ordering would be
> CPU_TYPE then generic. There is not gray area. For example,
> I have an athlon processor, so libgmp.a would have a preferred
> order of athlon, generic.
It's not just for libgmp, but for other parts of the system too (like
openssl).
For example, what happens if you have a pentium pro, but there are no
ppro optimisations in a particular program - but there are pentium
optimisations. Obviously you would want those as a fallback.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message