[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 13 Jul 2015 19:00:15 +0200
From: Agnieszka Bielec <bielecagnieszka8@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: PHC: Lyra2 on GPU
2015-07-12 16:39 GMT+02:00 Solar Designer <solar@...nwall.com>:
> On Mon, Jul 06, 2015 at 06:07:34PM +0200, Agnieszka Bielec wrote:
>> is it ok? and in pomelo also remove generic pomelo?
>>
>> Benchmarking: Lyra2 [Blake2/SSE2]... (8xOMP) DONE
>>
>> #define FORMAT_LABEL "Lyra2"
>> #define FORMAT_NAME ""
>>
>> #ifdef SIMD_COEF_64
>> #define ALGORITHM_NAME "Blake2/SSE2"
>> #else
>> #define ALGORITHM_NAME "Blake2"
>> #endif
>
> No, this is not quite it yet. We don't use slashes to separate
> crypto algorithm names from SIMD instruction set names and such.
> We use spaces there.
>
> More importantly, it's not necessarily "SSE2" if SIMD_COEF_64 is
> defined. It could as well be "AVX" or something else, depending on the
> build. Your task is to ensure proper reporting, including for things
> like "SSE2" vs. "AVX".
what if algorithm in most cases uses see and uses ssse only a little ?
Will my code be compiled to AVX if I have sse2 intrinsics in the code
and I have defined __AVX__ ?
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.
