[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31a99a4214bb11bba2760655ac30b1ee@smtp.hushmail.com>
Date: Wed, 10 Apr 2013 12:40:56 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: [patch] sse/xop implementation of raw-sha256
On 10 Apr, 2013, at 3:42 , Jeremi Gosney <epixoip@...dshell.nl> wrote:
> On 4/9/2013 11:29 AM, magnum wrote:
>> On 9 Apr, 2013, at 19:00 , Jeremi Gosney <epixoip@...dshell.nl> wrote:
>>> I was surprised to learn there was no SIMD implementation of SHA2 in
>>> JTR, so I wrote one. I've completed SHA256, and have attached a patch
>>> for it. I will begin work on SHA512 shortly.
>> Cool, thanks! Committed now.
>
> Excellent, thanks!
>
> So, I mentioned in my last post that I was unsatisifed with the way I
> was loading plaintext candidates. I've attached a new patch that uses
> SSE4.1 (if available) for more efficient loading. I am much more
> satisfied with this, and it's good for another ~ 1 MH/s. I also did some
> minor cleanup, and removed the __GNUC__ check per Solar's guidance.
Committed now, as well as a patch that make it a non-plugin that loads only on archs that support it. I made it load with higher precedence than the vanilla format (Tavis' SHA1 doesn't, because it has limited length support - and the alternate format also use SSE2).
magnum
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.
