Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 16 Apr 2012 18:10:49 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Xsha512 OpenCL Code

myrice -

On Mon, Apr 16, 2012 at 07:28:32PM +0800, myrice wrote:
> On Sun, Apr 15, 2012 at 10:31 AM, Solar Designer <solar@...nwall.com> wrote:
> > user@...l:~/john/myrice-JtR/src$ ../run/john -te -fo=xsha512-opencl -pla=1
> > OpenCL platform 1: AMD Accelerated Parallel Processing, 2 device(s).
> > Using device 0: Tahiti
> > Compilation log: /tmp/OCLbj5mOR.cl(121): warning: type qualifier specified
> > more than once
> >        __global uint64_t* hash, uint32_t offset, __constant const char*
> > salt)
> >                                                             ^
> >
> > /tmp/OCLbj5mOR.cl(224): warning: type qualifier specified more than once
> >        __constant const char *salt)
> >                   ^
> > 
> > Benchmarking: Mac OS X 10.7+ salted SHA-512 [OpenCL]... FAILED (get_hash[0](0))
> 
> It is strange. On my NVIDIA card, if I remove the __constant, there will
> be errors when compile it.

I don't care about the compiler warnings as much as I do about the
failed self-test.  I think we have at least two separate problems here.
In fact, when I remove the "const" keywords from these two places, the
warnings are gone, but the self-test still fails in the same way.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ