lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Mar 2014 01:13:13 +0000
From: Samuel Neves <>
Subject: Re: [PHC] Supporting AVX2/SSE2 or not with a single binary

On 20-03-2014 00:54, Bill Cox wrote:
> One reason I think we see applications running without SSE/AVX2
> support is that operating systems don't want to support two versions
> of a binary, and they have to support older machines.  The Blake2 code
> I've read does not provide for a single binary that supports both - I
> have to link either to the blake2-ref code or the blake2-sse code.  My
> TwoCats code has inherited this limitation, since I used the Blake2
> code as a roadmap for figuring out how SSE2 works.

libb2 [1] does have basic support for runtime CPU feature detection. In
general, though, this is annoying to support in a portable way due to
different ways to invoke cpuid between compilers, operating system
support (you may have an AVX-capable system but the OS may not save ymm
registers across context switches), and so on.


Powered by blists - more mailing lists