05750f23ae
This was reverted a second time because it ended up always setting the final argument to CRYPTO_gcm128_init to zero, which disabled some acceleration of GCM on ≥Haswell. With this update, that argument will be set to 1 if |aes_hw_*| functions are being used. Probably this will need to be reverted too for some reason. I'm hoping to fill the entire git short description with “Revert”. Change-Id: Ib4a06f937d35d95affdc0b63f29f01c4a8c47d03 Reviewed-on: https://boringssl-review.googlesource.com/28484 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
---|---|---|
.. | ||
aes-586.pl | ||
aes-armv4.pl | ||
aes-x86_64.pl | ||
aesni-x86_64.pl | ||
aesni-x86.pl | ||
aesp8-ppc.pl | ||
aesv8-armx.pl | ||
bsaes-armv7.pl | ||
bsaes-x86_64.pl | ||
vpaes-x86_64.pl | ||
vpaes-x86.pl |