Date: Wed, 15 Apr 2015 08:08:42 -1000 From: Agnieszka Bielec <bielecagnieszka8@...il.com> To: john-dev@...ts.openwall.com Subject: Re: [GSoC] John the Ripper support for PHC finalists 2015-04-15 7:42 GMT-10:00 Alexander Cherepanov <ch3root@...nwall.com>: > 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? I can modify pomelo to avoid problems with sizes in various platforms (I don't mean opencl) but if the author of pomelo use unsigned long long, should I change it to uint64 ?
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.