On 08/23/2014 10:19 PM, Colin Percival wrote:
On 08/23/14 13:00, Dmitry Chestnykh wrote: This is correct: It's checking for compiler support, not whether the current CPU can run the code, since you might build on one system and run the binary on another. Good, everything it working -- the build code is detecting that your compiler supports AESNI, is building support for it into the spipe binary, but then when spipe is run it is detecting that your CPU does not support AESNI and is using the OpenSSL code instead.
Oh, cool -- I like it when the actual CPI feature support is detected during runtime! Thanks.
-- Dmitry Chestnykh