[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+TsHUC3j_PFUPabYXOQFfpvwMb2D1KPRnAykMsUkxGGuT45gg@mail.gmail.com>
Date: Wed, 5 Sep 2012 08:52:40 +0530
From: Sayantan Datta <std2048@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: bitslice DES on GPU
On Wed, Sep 5, 2012 at 3:53 AM, magnum <john.magnum@...hmail.com> wrote:
> On 4 Sep, 2012, at 18:14 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>
> > On 09/04/12 at 08:05pm, Solar Designer wrote:
> >> On Tue, Sep 04, 2012 at 08:12:09PM +0530, Sayantan Datta wrote:
> >>> I have ported the non-LM bitslice DES implementation to opencl with
> >>> DES_BS_EXPAND set to 1.
>
> There was problems with this patch. First, its format struct was
> incompatible with bleeding-jumbo (I really wish we could have a couple of
> releases so we get rid of this MESS). I fixed that.
>
> Thanks.
> Second, you include .c files from the run/ directory - not placed there by
> build, but placed there permanently. While it worked on bull, it did not on
> OSX:
>
> mbpr-osx:src magnum$ ../run/john -t -fo:des-opencl -dev=1
> OpenCL platform 0: Apple, 2 device(s).
> Using device 1: GeForce GT 650M
> Compilation log: <program source>:304:10: fatal error: 'opencl_sboxes.c'
> file not found
> #include "opencl_sboxes.c"
> ^
>
> Error building kernel. Returned build code: -11. DEVICE_INFO=130
> OpenCL error (CL_BUILD_PROGRAM_FAILURE) in file (common-opencl.c) at line
> (139) - (clBuildProgram failed.)
>
>
> Not quite sure why. We have other formats that place opencl_*.h files in
> src that get copied to run/ when building and that works fine. So I tried
> renaming them (including references inside them and the kernel) and it now
> works fine. Please pull.
>
> magnum
>
I'll try to use the .h files. However it might require those .c files too
because the functions are in those files.
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.
