john-users - Re: bitslice DES on AVX

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110223084032.GA23503@openwall.com>
Date: Wed, 23 Feb 2011 11:40:32 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: bitslice DES on AVX

Hi,

I've attached the updated patch (john-1.7.6-avx-2), and I also uploaded
it to the wiki:

http://openwall.info/wiki/john/patches

This adds linux-x86-64-avx and linux-x86-64-xop make targets to build
JtR for latest Intel and future AMD CPUs, respectively.  Such builds will
make use of the new AVX and optionally XOP instructions to hopefully
achieve much better performance at bitslice DES.

By default, 256-bit vectors are used, but 128-bit ones are available as
an option by changing an "#if 1" to "#if 0" in x86-64.h.

This code requires recent gcc and binutils.  gcc may be built locally:
http://openwall.info/wiki/internal/gcc-local-build

Everything except for 256-bit XOP should also build with recent
versions of other C compilers for x86-64, such as with Intel's - but I
did not test this.  If you do, please post to john-users.

AVX builds (both 256- and 128-bit) are only tested under Intel's
Software Development Emulator so far.  They work fine.

XOP is only tested that it compiles (and that its disassembly looks sane
at first glance, and that it fails under the AVX-only emulator).

If you try this out on a real CPU or on a XOP emulator, please post your
results to john-users.

Thanks,

Alexander

View attachment "john-1.7.6-avx-2.diff" of type "text/plain" (5844 bytes)

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.