You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
wanggang
5ff49cc5f4
|
6 years ago | |
|---|---|---|
| .. | ||
| 090 | 6 years ago | |
| 091 | 6 years ago | |
| x86 | 6 years ago | |
| 5.lnx | 6 years ago | |
| 100.lnx | 6 years ago | |
| 100.nt | 6 years ago | |
| 200.lnx | 6 years ago | |
| 486-66.dos | 6 years ago | |
| 486-66.nt | 6 years ago | |
| 486-66.w31 | 6 years ago | |
| 586-085i.nt | 6 years ago | |
| 586-100.LN3 | 6 years ago | |
| 586-100.NT2 | 6 years ago | |
| 586-100.dos | 6 years ago | |
| 586-100.ln4 | 6 years ago | |
| 586-100.lnx | 6 years ago | |
| 586-100.nt | 6 years ago | |
| 586-100.ntx | 6 years ago | |
| 586-100.w31 | 6 years ago | |
| 586-1002.lnx | 6 years ago | |
| 586p-100.lnx | 6 years ago | |
| 686-200.bsd | 6 years ago | |
| 686-200.lnx | 6 years ago | |
| 686-200.nt | 6 years ago | |
| L1 | 6 years ago | |
| R4400.t | 6 years ago | |
| R10000.t | 6 years ago | |
| aix.t | 6 years ago | |
| aixold.t | 6 years ago | |
| alpha.t | 6 years ago | |
| alpha400.t | 6 years ago | |
| cyrix100.lnx | 6 years ago | |
| dgux-x86.t | 6 years ago | |
| dgux.t | 6 years ago | |
| hpux-acc.t | 6 years ago | |
| hpux-kr.t | 6 years ago | |
| hpux.t | 6 years ago | |
| p2.w95 | 6 years ago | |
| pent2.t | 6 years ago | |
| readme | 6 years ago | |
| s586-100.lnx | 6 years ago | |
| s586-100.nt | 6 years ago | |
| sgi.t | 6 years ago | |
| sparc.t | 6 years ago | |
| sparc2 | 6 years ago | |
| sparcLX.t | 6 years ago | |
| usparc.t | 6 years ago | |
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.