Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Mar 2015 21:12:42 +0300
From: Lei Zhang <>
Subject: Re: [GSoC] building JtR for MIC

Hi Alexander,

While trying to build john-jumbo for MIC, I encountered some issues which recovered potential bugs in icc (Intel compiler).

There’s a file named ‘pp.c’ which failed to compile for MIC, and the error is related to the use of type ‘__uint128_t’.
When compiling this file, icc tries to generate some SSE instructions for better performance. But SSE is not supported on MIC, and hence the compile error.

I’ve posted this issue to the Intel’s developer zone, and I’m still waiting for response. <>

Interestingly, I’ve also found another potential bug in icc while building john-jumbo. You may take a look as well: <>


> 在 2015年3月7日,下午11:25,Solar Designer <> 写道:
> On Sat, Mar 07, 2015 at 11:15:57PM +0800, ??? ??? wrote:
>> I managed to build JtR for MIC on a server in our lab, and get it running the benchmark. 
> Great.
>> The version of JtR I downloaded is 1.8.0. I added a target for MIC in the Makefile and created file mic.h (copied from ia64.h) to get it built for MIC. The model of Intel MIC card used is 5110P.
> This is basically duplicate work to what I reported on here:
> That's fine.
>> Below is the result of the benchmark:
>> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????
>> Benchmarking: descrypt, traditional crypt(3) [DES 64/64]... DONE
>> Many salts:	179008 c/s real, 179008 c/s virtual
>> Only one salt:	172812 c/s real, 172812 c/s virtual
> This is just one core running the non-SIMD code.
>> Any suggestions?
> Since the core tree uses SIMD for bitslice DES only, and since we
> already have MIC intrinsics for it (see my posting referenced above), in
> the GSoC project you'd need to work solely with the jumbo tree.
> So please try to get jumbo to build for and run on MIC, and report back
> in here.  Ideally, magnum should merge my MIC support changes referenced
> above into jumbo first, but this is not crucial since you clearly have
> the experience to start without that as well.
> You may also experiment with (from CVS, or I may send you the
> tarball), just to have something inbetween your clean 1.8.0 build and
> the jumbo build.
> Thanks,
> Alexander

Content of type "text/html" skipped

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.