Signal-Android/jni/openssl/crypto/bn/asm
..
x86
README
alpha-mont.pl
armv4-gf2m.S
armv4-gf2m.pl
armv4-mont.S
armv4-mont.pl
bn-586.S
bn-586.pl
bn-mips.S
co-586.S
co-586.pl
ia64-mont.pl
ia64.S
mips-mont.S
mips-mont.pl
mips.pl
mips3-mont.pl
mips3.s
modexp512-x86_64.S
modexp512-x86_64.pl
pa-risc2.s
pa-risc2W.s
parisc-mont.pl
ppc-mont.pl
ppc.pl
ppc64-mont.pl
s390x-gf2m.pl
s390x-mont.pl
s390x.S
sparcv8.S
sparcv8plus.S
sparcv9-mont.pl
sparcv9a-mont.pl
via-mont.pl
x86-gf2m.S
x86-gf2m.pl
x86-mont.S
x86-mont.pl
x86.pl
x86_64-gcc.c
x86_64-gf2m.S
x86_64-gf2m.pl
x86_64-mont.S
x86_64-mont.pl
x86_64-mont5.S
x86_64-mont5.pl

README

<OBSOLETE>

All assember in this directory are just version of the file
crypto/bn/bn_asm.c.

Quite a few of these files are just the assember output from gcc since on 
quite a few machines they are 2 times faster than the system compiler.

For the x86, I have hand written assember because of the bad job all
compilers seem to do on it.  This normally gives a 2 time speed up in the RSA
routines.

For the DEC alpha, I also hand wrote the assember (except the division which
is just the output from the C compiler pasted on the end of the file).
On the 2 alpha C compilers I had access to, it was not possible to do
64b x 64b -> 128b calculations (both long and the long long data types
were 64 bits).  So the hand assember gives access to the 128 bit result and
a 2 times speedup :-).

There are 3 versions of assember for the HP PA-RISC.

pa-risc.s is the origional one which works fine and generated using gcc :-)

pa-risc2W.s and pa-risc2.s are 64 and 32-bit PA-RISC 2.0 implementations
by Chris Ruemmler from HP (with some help from the HP C compiler).

</OBSOLETE>