Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100509212144.GA15351@openwall.com>
Date: Mon, 10 May 2010 01:21:44 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: OpenMP

On Sun, May 09, 2010 at 12:49:01PM -0400, Erik Winkler wrote:
> For MacOSX, the command is Otool -L,
> 
> $ Otool -L john
> john:
> 	/usr/local/lib/libgomp.1.dylib (compatibility version 2.0.0, current version 2.0.0)
> 	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.1)

So I guess that /usr/local/lib/libgomp.1.dylib came from Xcode (and is
not available on systems without Xcode installed).

> Here is what I get when running the non-OpenMP john on both cores:
> 
> Benchmarking: OpenBSD Blowfish (x32) [32/64 X2]... 
> Benchmarking: OpenBSD Blowfish (x32) [32/64 X2]... 
> 
> DONE
> Raw:	599 c/s real, 615 c/s virtual
> 
> DONE
> Raw:	606 c/s real, 617 c/s virtual

This is very close to your 1211 c/s with OpenMP, so the efficiency is
close to 100% - but we can't easily tell just how close it is.  There
appears to be some load on the system (perhaps from the GUI), which
appears to be in excess of any efficiency loss from the OpenMP build.

> I did note the following compile error when compiling SSE2 version:
> 
> gcc -c -Wall -O2 -fomit-frame-pointer -fopenmp -m32 -funroll-loops BF_std.c
> BF_std.c: In function ?BF_std_crypt?:
> BF_std.c:687: error: ?BF_body? not specified in enclosing parallel
> BF_std.c:607: error: enclosing parallel
> make[1]: *** [BF_std.o] Error 1
> make: *** [macosx-x86-sse2] Error 2

Indeed.  OK, you got me to make a 32-bit build of gcc 4.5.0 as well and
to complete that part of the patch.  The above should be fixed in
1.7.5-omp-2, which I've just uploaded to:

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

Thanks,

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.