[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 19 Feb 2013 19:10:02 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Bleeding device selection
On 19 Feb, 2013, at 18:43 , Sayantan Datta <std2048@...il.com> wrote:
> On Tue, Feb 19, 2013 at 6:51 AM, magnum <john.magnum@...hmail.com> wrote:
> On 18 Feb, 2013, at 23:40 , magnum <john.magnum@...hmail.com> wrote:
> > I committed this along with a fix for pwsafe. The latter now uses a split kernel, but only asked for max workgroup size for one of the kernels. The good thing about my crappy CPU driver is it triggers such bugs.
> >
> > Unfortunately it also triggers it in DES and I can't find how/where to fix it:
> >
> > Benchmarking: Traditional DES [OpenCL]... OpenCL error (CL_INVALID_WORK_GROUP_SIZE) in file (opencl_DES_bs_b.c) at line (410) - (Enque Kernel Failed)
>
> I managed to fix that DES problem. Committed to unstable-jumbo too.
>
> magnum
> Hi guys,
>
> I am aware of the problems regarding des-opencl and bf-opencl in bleeding jumbo. However they should work fine under unstable jumbo. Are we now trying to merge the two branches ?
Not yet. I fixed the worst problem in unstable (DES now asks device for max LWS). Should be good enough for Jumbo-8 now. Claudio seems to have fixed the worst issues in bleeding.
magnum
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.
