[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <552EA2F3.2070400@openwall.com>
Date: Wed, 15 Apr 2015 20:42:11 +0300
From: Alexander Cherepanov <ch3root@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] John the Ripper support for PHC finalists
On 30.03.2015 12:11, magnum wrote:
> Agnieszka, please note that in OpenCL an int is always 32-bit and long
> is always 64-bit. Long long is not used but is reserved; it may be used
> in the future eg. for 128-bit.
>
> So when porting C code, basically ULL should always be UL and you can
> replace all "long long" with long. On the same note, some reference code
> use long where they really only need 32-bit (because that's what you
> need to use to be really portable) and replacing that with int in a
> kernel can give a very significant speed boost.
Perhaps it's better to use types like uint32_t etc. if we know which
types we need exactly and target platforms with different sizes?
--
Alexander Cherepanov
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.
