Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM³<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=453.msg5774#msg5774">Quote from: BlackEye on July 25, 2010, 10:12:23 PM</a></div><div class="quote">I was able to integrate the SHA256 functionality from Crypto++ 5.6.0 into Bitcoin. &nbsp;This is the fastest SHA256 yet using the SSE2 assembly code. &nbsp;Since Bitcoin was sending unaligned data to the block hash function, I had to change the MOVDQA instruction to MOVDQU.<br/><br/>I think using the SHA256 functionality from Crypto++ 5.6.0 is the way forward right now.<br/></div>I added a subset of the Crypto++ 5.6.0 library to the SVN. &nbsp;I stripped it down to just SHA and 11 general dependency files. &nbsp;There shouldn't be any other crypto in there other than SHA.<br/><br/>I aligned the data fields and it worked. &nbsp;The ASM SHA-256 is about 48% faster. &nbsp;The combined speedup is about 2.5x faster than version 0.3.3.<br/><br/>I guess it's using SSE2. &nbsp;It automatically sets its build configuration at compile time based on the compiler environment.<br/><br/>It looks like it has some SSE2 detection at runtime, but it's hard to tell if it actually uses it to fall back if it's not available. &nbsp;I want the release builds to have SSE2. &nbsp;SSE2 has been around since the first Pentium 4. &nbsp;A Pentium 3 or older would be so slow, you'd be wasting your electricity trying to generate on it anyway.<br/><br/>This is SVN rev 114.</div> text/html