Date: Sun, 5 May 2013 16:57:32 -0400 From: <jfoug@....net> To: john-dev@...ts.openwall.com Cc: Dhiru Kholia <dhiru.kholia@...il.com> Subject: Re: SSE code in pbkdf2_hmac_sha1 and pbkdf2_hmac_sha256 code Magnum found a problem building encfs without SSE. That was a late change for me. it was not on my list of ones todo, and has actually been removed from my build tree since last August (had serious portability issues with VC). I found it when pulling a clean git tree on x64, patching it, and building. But I think only the sse part (that I added), got properly tested. The non-sse was still in older format. I will get that fixed soon. Jim. ---- Dhiru Kholia <dhiru.kholia@...il.com> wrote: > On 05/05/13 at 11:39am, jfoug@....net wrote: > > I have modified both of these headers. They now build with either > > oSSL code, or with SSE intrinsic code, depending upon the build > > target. > > On my PC, zip went from 650 to about 1500 with the original change. > > Then to about 3100 after my changes, (oSSL build), and about 9k for > > SSE2 builds. So from 650 to 9k is not a bad speedup ;) > > Great work Jim :-) > > -- > Dhiru
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.