[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B982488.7010800@bredband.net>
Date: Thu, 11 Mar 2010 00:00:24 +0100
From: "Magnum, P.I." <rawsmooth@...dband.net>
To: john-users@...ts.openwall.com
Subject: Re: Extended MPI support
> mpicc -c -Wall -O2 -fomit-frame-pointer -I/usr/local/include
> -L/usr/local/lib -funroll-loops status.c
> status.c: In function ‘status_get_cps_avg’:
> status.c:154: error: ‘MPI_UNSIGNED_LONG_LONG’ undeclared (first use in this
> function)
> status.c:154: error: (Each undeclared identifier is reported only once
> status.c:154: error: for each function it appears in.)
> make[1]: *** [status.o] Error 1
>
> replace MPI_UNSIGNED_LONG_LONG with just MPI_UNSIGNED_LONG on line 154 of
> status.c and all is golden.
Thanks. MPI_UNSIGNED_LONG_LONG works fine with MPICH2, are you using
OpenMPI? I'm not sure you're safe though. I'm a complete noob at
datatypes on different platforms, but I expect MPI_UNSIGNED_LONG to be
just 32 bit on some, while LONG_LONG should be 64 bit. Maybe on 64-bit
systems MPI_UNSIGNED_LONG will always do?
The reason for needing 64 bit is that it holds the total number of
crypts performed since session started. For a fast algorithm a 32 bit
will roll over.
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.
