[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150311220756.GA20840@openwall.com>
Date: Thu, 12 Mar 2015 01:07:56 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: bitslice MD*/SHA*, AVX2
On Wed, Mar 11, 2015 at 10:45:19PM +0100, magnum wrote:
> On 2015-03-11 22:21, Solar Designer wrote:
> > BTW, it appears that we don't currently use this optimization. Not even
> > in the copy of my portable MD5 implementation in JtR, which I've since
> > updated to include this optimization here:
> >
> > http://openwall.info/wiki/people/solar/software/public-domain-source-code/md5
> >
> > In my testing, this might not be beneficial on 2-operand archs such as
> > plain x86, but it should be on 3-operand archs such as AVX. So we
> > should update the code in sse-intrinsics.c, and benchmark. And we should
> > update the plain C code anyway, such as for non-x86 archs (which are
> > mostly 3-operand RISC).
> >
> > magnum, Jim?
>
> Yeah... unless we have some GSoC candidate wanting to show his/her
> teeth? That would be a good start!
OK, I don't mind keeping this on hold until GSoC student application
period ends. Would you track it, so it doesn't get forgotten in case no
GSoC candidate takes care of it?
Alexander
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.
