[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c596cbe31a136e61516cef562b212f7@smtp.hushmail.com>
Date: Tue, 14 Apr 2015 23:45:38 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: AVX2/AVX512 support
I have now merged Lei's and mine AVX2/AVX512/MIC code into the main
bleeding-jumbo branch. Everything works fine except dynamic. In fact,
dynamic is totally left out from the build (unless the new option
--enable-experimental-code is given to ./configure). The reason I went
that path is we haven't heard from Jim for a while and it started to get
painful having diverging branches.
A user who just makes a vanilla autoconf build will get AVX2 but no
dynamic format. Warning notices will be printed and details are in
doc/BUGS. To get a usable dynamic format, just rebuild for AVX instead.
I think this will be OK for now. I did try fixing dynamic but gave up
when I realized some parts of the code stuffs four 8-bit length bytes
into one 32-bit integer. Doesn't scale that well with 8x and higher. To
Jim's defense that is some legacy from the early MMX assembler code (I
think) but anyway some code simply has to be rewritten.
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.
