]> git.ipfire.org Git - thirdparty/openssl.git/commit
Don't compile AESNI code if we're not AESNI capable
authorMatt Caswell <matt@openssl.org>
Wed, 5 Feb 2020 17:42:40 +0000 (17:42 +0000)
committerMatt Caswell <matt@openssl.org>
Sat, 8 Feb 2020 00:02:13 +0000 (00:02 +0000)
commit87d3bb8e861e54e2549e848a1adee6d2df9ed603
tree6ffe168dbf3110a8dcce506f3a8333aedb5fbf6e
parente89ffd23c37905574b3beab163b298dabb9f7a20
Don't compile AESNI code if we're not AESNI capable

Compile failures were occuring on systems that weren't AESNI capable
because the detection wasn't quite right in a couple of files.

This fixes a run-checker build failure for the 386 compile option.

Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/11022)
providers/implementations/ciphers/cipher_aes_cbc_hmac_sha.h
providers/implementations/ciphers/cipher_aes_cbc_hmac_sha1_hw.c
providers/implementations/ciphers/cipher_aes_cbc_hmac_sha256_hw.c