[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7B683130651A4E5F9488A774BF78BDE0@D9VGLK61>
Date: Sun, 8 May 2011 20:26:48 -0500
From: "JimF" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: Re: New patches
well, I am gettint Intel C++ Stuio XE for Linux. It has icc icc++ and vtune
(and a couple other things). I have used VTune before. It is one hell of a
tool. I am not sure how well it will work in an athon enviroment, but for
finding where to reorder instructions, and such, it is wonderful.
Hopefully, this will install easily, and allow me to test better, and even
build some cracking sw that really is faster than what I have had in the
past.
Jim.
----- Original Message -----
From: "magnum" <rawsmooth@...dband.net>
To: <john-dev@...ts.openwall.com>
Sent: Sunday, May 08, 2011 6:57 PM
Subject: Re: [john-dev] New patches
> On 2011-05-06 22:52, magnum wrote:
>> I just uploaded a couple of patches to the wiki:
>>
>> john-1.7.7-jumbo-1-fullmpi-10.diff.gz
>> * Fixed a silly off-by-one bug introduced in fullmpi-9.
>> * Fixed a very old bug (actually 1.7.5-mpi10) which hasn't surfaced
>> until today. Missed initialization after mem_alloc_tiny() when applying
>> the mpi node id to the recovery file name. I am amazed it never surfaced
>> until now (you would have noticed).
>> * Added some logic for OMP + MPI, configurable in john.conf. As shipped,
>> OMP will be disabled if you use MPI to start several processes. In
>> multi-host, multi-core environments, there can be situations where you
>> want both (starting one MPI process per host, and one OMP thread per
>> core). This is supported after changing a line in john.conf.
>> Notices about this are also printed, but can be muted with another
>> john.conf setting.
>
> I just uploaded the same stuff, rebased onto jumbo-2-RC1
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.
