[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f05cce39c33c6fd5b97cf61e29fbe337@smtp.hushmail.com>
Date: Sat, 30 May 2015 01:59:46 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: bitslice SHA-256
On 2015-05-29 20:13, Alain Espinosa wrote:
> Hand-crafted AVX2 assembly code done for "normal" SHA256. Performance
> in a core i5-4670 3.4GHz, single thread:
>
> - 23.7 millions keys per second. 87% faster than the bitslice one
> with AVX2 intrinsics.
Alain, Solar,
The bitslice track is very interesting, but on a side note: What's the
main cause for this huge difference between normal SHA256 implemented in
assembly versus intrinsics? Perhaps the optimizer make some poor
choices? Could we learn something from analyzing compiled intrinsics and
tweak the source a little?
OTOH I think the JtR implementation of SHA256 is a lot faster than 12.5M
keys/s - benchmarking on well (i7-4770K 3.5GHz) shows over 19M. but we
might not compare apples to apples.
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.
