Crypto++ 5.6 ?

[j16sdiz]

I saw you are using a modified cryptopp 5.6.0,  which disable SSE2 on 32-bit x86.

On the official website, there is a newer version 5.6.1 which fix a few SHA-256 related bug. I guess you may be interested:

- fixed several bugs in the SHA-256 x86/x64 assembly code:
--- incorrect hash on non-SSE2 x86 machines on non-aligned input
--- incorrect hash on x86 machines when input crosses 0x80000000
--- incorrect hash on x64 when compiled with GCC with optimizations enabled

[BioMike]

For the gentoo ebuild I have been using the original thing for some time now (Gentoo policy is not to use bundled libs, as they are a security hazard). No problems encountered in more then a half year.

[jgarzik]

This patch updates part of Crypto++ in bitcoin to upstream:
http://yyz.us/bitcoin/patch.bitcoin-asmfix1

[j16sdiz]

I have patched the  "bitcoinr" to use system provided crypto, here is the result:

CPU:  Premium III Mobile  (yes, i know this is very very old)
Compiled with gcc 4.4,  -O3 -msse

the cryptopp 5.6.0 in bitcoinr tree:   133khash/s
the cryptopp 5.6.1 (provided in debian):   200khash/s


Here is the patch to use system-provided cryptopp (if available, with fallback)
https://github.com/j16sdiz/bitcoin-pool/commit/121a0a570bed15fc347cff091e740a02bd8e1a3f

[BioMike]

I have patched the  "bitcoinr" to use system provided crypto, here is the result:

CPU:  Premium III Mobile  (yes, i know this is very very old)
Compiled with gcc 4.4,  -O3 -msse

the cryptopp 5.6.0 in bitcoinr tree:   133khash/s
the cryptopp 5.6.1 (provided in debian):   200khash/s


Here is the patch to use system-provided cryptopp (if available, with fallback)
https://github.com/j16sdiz/bitcoin-pool/commit/121a0a570bed15fc347cff091e740a02bd8e1a3f

That's quite a difference.

[jgarzik]

I have patched the  "bitcoinr" to use system provided crypto, here is the result:

CPU:  Premium III Mobile  (yes, i know this is very very old)
Compiled with gcc 4.4,  -O3 -msse

the cryptopp 5.6.0 in bitcoinr tree:   133khash/s
the cryptopp 5.6.1 (provided in debian):   200khash/s

Out of curiosity, what speed do you get from various algorithms in the CPU miner?  That also uses Crypto++ code.

[j16sdiz]

the cryptopp 5.6.0 in bitcoinr tree:   133khash/s
the cryptopp 5.6.1 (provided in debian):   200khash/s

Sorry, I was mixing up some binaries. The improvement was not that great. -- in fact, that was statistically insignificant.