[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a4e016ee6bad74f1c216aad17ffc4f2@smtp.hushmail.com>
Date: Mon, 4 Feb 2013 22:31:51 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: OpenCL problems
What happens without that show_usage cludge? Does it fail to give proper usage output? Ah no, I think I see now: this way it wont even list the formats unless we have a proper device, right?
I think we should think about this before doing too much. Maybe we should list the formats anyway. Or maybe not. Argh.
The simplest might be to drop this idea and just do like unstable: As long as you don't use an OpenCL format, it's fine not having any working platform and/or device. Only when you do, you'll get a device/platform error.
magnum
On 4 Feb, 2013, at 22:22 , Claudio André <claudioandre.br@...il.com> wrote:
> Em 04-02-2013 19:06, Claudio André escreveu:
>> Em 04-02-2013 18:46, magnum escreveu:
>>> [I felt I should cc the list, this might be of interest to someone. This is about the bleeding-jumbo tree.]
>>>
>>> How about returning the number of devices? Then we could do this *inside* john_register_all():
>>
>> There is a john_register_all(); at line 617, before opt_init() [this initializes what i need to parse, right?];
>>
>> Can I ignore this case --help usecase?
>>
>> Claudio
>
> Wrong patch attached. What we should do with opt_init() and the first call to john_register_all()?
>
> Claudio
> <ver.txt>
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.
