FAT GMP 5 binaries

[Karl Hasselstrom]

--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2003-05-14 14:53:44 +0200, Torbjorn Granlund wrote:

> We need to decide what routines to put in __gmp_cpuvec. All GMP
> rouines is one choice. All mpn routines or a subset of mpn rouines
> are other choices.

The routines that have been hand-coded in assembly are obvious
candidates for this. For routines written in C, would the speedup be
worth the effort?

> Internal GMP calls would use __gmp_cpuvec[RNUM_GMP_ADDMUL_1]
> directly, via some gmp-impl.h macros. The overhead would be a few
> cycles.

If a large subset of the GMP functions are cpu-specific, these entry
decisions need not be done very often; code that has been compiled
specifically for processor Foo already knows that it wants the Foo
version of whatever subroutines it calls, so the decision can be done
at compile-time. The decision only has to be done at run-time when a
function _not_ in __gpm_cpuvec calls one that _is_ in there.

--=20
Karl Hasselstr=F6m, kha@treskal.com
      www.treskal.com/kalle

--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+wkUFN7iPzXSoOQoRAtp0AJ4/CsKxCcb3rezDFu5OTbNUI8cusgCfWumD
5wbRxSD9zYi426kbO0M1EsQ=
=NCYn
-----END PGP SIGNATURE-----

--tThc/1wpZn/ma/RB--