[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <53023EE4.8050909@gmail.com>
Date: Mon, 17 Feb 2014 13:55:00 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: sha512crypt-opencl format fails in xeon phi coprocesor
> === Testing sha512crypt-opencl on MIC ===
> Device 1: Intel(R) Many Integrated Core Acceleration Card
> Exit code: 139
>
> 139 means segfault.
>
> Now that I've tried bleeding-jumbo on our 5110P, I am getting results
> similar to what Mr Dupito posted.
>
> I suggest that we create you an account on our machine with the 5110P,
> and you debug the issue.
It is a good path to follow, but I saw a lot of errors in raw formats,
event MD4 and MD5. And it doesn't make sense, "they are very simple code".
Intel OpenCL driver/compiler creativity!?!?!
That said, seems to me OpenCL and MIC are not going to be a production
quality target for a while. I might solve the problem with raw formats,
but I'm not confident things are going to be much better than now.
Claudio
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.
