> Finally, should I be able to build the Crypto++ library (not the test > program project) using STLport in "_STLP_NO_IOSTREAMS" mode? Because > that seems to not be working, in that I get a compile-time error from > STLport that is [apparently] triggered off of *some* reference to > iostreams...
Iostream has to be there. The linker needs to see it, but should be able to optimize it away if you are just using hash functions. If that isn't happening, then something is wrong. Oh, btw, the 151KB size is using the default standard C++ library, not STLport. > BTW, the speed of these hash funcs is really impressive - my previous > implementation (from LibTomCrypt) fell down badly on the SHA-512, and > particularly Whirlpool; neither could keep up with disk reading speeds > of ~65 MB/s, but the Crypto++ versions are faster than disk (as noted in > the OP, 77 MB/s for Whirlpool!). SHA-512 and Whirlpool both need to use 64-bit registers for optimal speed, which is why they are typically much faster on 64-bit CPUs than on 32-bit CPUs. However in 32-bit mode x86, it is possible to use MMX/XMM registers to speed up those algorithms. Assembly language code was introduced in version 5.5 to do so. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
