Jay Sistar
b551e772ee
Adding OpenSSL for HTTPS.
|
10 年之前 | |
|---|---|---|
| .. | ||
| 090 | 10 年之前 | |
| 091 | 10 年之前 | |
| x86 | 10 年之前 | |
| 100.lnx | 10 年之前 | |
| 100.nt | 10 年之前 | |
| 200.lnx | 10 年之前 | |
| 486-66.dos | 10 年之前 | |
| 486-66.nt | 10 年之前 | |
| 486-66.w31 | 10 年之前 | |
| 5.lnx | 10 年之前 | |
| 586-085i.nt | 10 年之前 | |
| 586-100.LN3 | 10 年之前 | |
| 586-100.NT2 | 10 年之前 | |
| 586-100.dos | 10 年之前 | |
| 586-100.ln4 | 10 年之前 | |
| 586-100.lnx | 10 年之前 | |
| 586-100.nt | 10 年之前 | |
| 586-100.ntx | 10 年之前 | |
| 586-100.w31 | 10 年之前 | |
| 586-1002.lnx | 10 年之前 | |
| 586p-100.lnx | 10 年之前 | |
| 686-200.bsd | 10 年之前 | |
| 686-200.lnx | 10 年之前 | |
| 686-200.nt | 10 年之前 | |
| L1 | 10 年之前 | |
| R10000.t | 10 年之前 | |
| R4400.t | 10 年之前 | |
| aix.t | 10 年之前 | |
| aixold.t | 10 年之前 | |
| alpha.t | 10 年之前 | |
| alpha400.t | 10 年之前 | |
| cyrix100.lnx | 10 年之前 | |
| dgux-x86.t | 10 年之前 | |
| dgux.t | 10 年之前 | |
| hpux-acc.t | 10 年之前 | |
| hpux-kr.t | 10 年之前 | |
| hpux.t | 10 年之前 | |
| p2.w95 | 10 年之前 | |
| pent2.t | 10 年之前 | |
| readme | 10 年之前 | |
| s586-100.lnx | 10 年之前 | |
| s586-100.nt | 10 年之前 | |
| sgi.t | 10 年之前 | |
| sparc.t | 10 年之前 | |
| sparc2 | 10 年之前 | |
| sparcLX.t | 10 年之前 | |
| usparc.t | 10 年之前 | |
readme
The 'times' in this directory are not all for the most recent version of
the library and it should be noted that on some CPUs (specifically sparc
and Alpha), the locations of files in the application after linking can
make upto a %10 speed difference when running benchmarks on things like
cbc mode DES. To put it mildly this can be very anoying.
About the only way to get around this would be to compile the library as one
object file, or to 'include' the source files in a specific order.
The best way to get an idea of the 'raw' DES speed is to build the
'speed' program in crypto/des.
the library and it should be noted that on some CPUs (specifically sparc
and Alpha), the locations of files in the application after linking can
make upto a %10 speed difference when running benchmarks on things like
cbc mode DES. To put it mildly this can be very anoying.
About the only way to get around this would be to compile the library as one
object file, or to 'include' the source files in a specific order.
The best way to get an idea of the 'raw' DES speed is to build the
'speed' program in crypto/des.