[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <506AEB47.2050907@gmail.com>
Date: Tue, 02 Oct 2012 10:25:27 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: OpenCL on OSX
Em 02-10-2012 05:18, magnum escreveu:
>
> I got silly build errors for all OpenCL functions (nb. not the kernels themselves, only helper functions) that did not use either static, inline or perhaps both. On other platforms, those keywords should be a no-op, functions are static and inline anyway afaik. Which one you use does not matter. Was there a difference?
No.
> On CPU, I get even more warnings (very noisy compiler but sometimes that is a good thing) and it fails:
>
>
> OpenCL platform 0: Apple, 2 device(s).
> Using device 0: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
> ...
>
> <program source>:270:5: warning: array index of '15' indexes past the end of an array (that contains 1 element)
> ctx->buffer->mem_32[15] = SWAP32(ctx->total * 8);
> ^ ~~
> /Users/magnum/src/john/src/opencl_cryptsha256.h:89:5: note: array 'mem_32' declared here
> uint32_t mem_32[1];
> ^
> /Users/magnum/src/john/src/opencl_cryptsha256.h:22:18: note: expanded from macro 'uint32_t'
> #define uint32_t unsigned int
> ^
>
> Local work size (LWS) 1, global work size (GWS) 1024
> Benchmarking: sha256crypt (rounds=5000) [OpenCL]... FAILED (get_hash[2](0))
There was a #ifdef sentence that could be "read wrong" by Apple
compiler. Let's see if it is fixed in my next try.
And i was thinking you did something like this (below) to source code in
unstable (as discussed on other thread). Should i do it now?
Me: I can change it to something like this:ctx->buffer[15].mem_32[0].
Magnum: I tried this now and it works fine (and warnings are gone).
Apple's OpenCL compiler is the noisiest I've seen. Sometimes that is a
good thing, sometimes not :)
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.
