Commit b837df32 authored by agl@chromium.org's avatar agl@chromium.org

Disable Poly1305 NEON code again.

The Poly1305 NEON code became live again with the BoringSSL switch. This
change disables it again in Chromium because of some broken phones.

We should really read /proc/cpuinfo and selectively disable, but this
change is simple and keeps the status-quo for now.

BUG=341598

Review URL: https://codereview.chromium.org/443523002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287630 0039d316-1c4b-4281-b951-d872f2087c98
parent 459cfad8
...@@ -62,6 +62,10 @@ class OpenSSLInitSingleton { ...@@ -62,6 +62,10 @@ class OpenSSLInitSingleton {
(android_getCpuFeatures() & ANDROID_CPU_ARM_FEATURE_NEON) != 0; (android_getCpuFeatures() & ANDROID_CPU_ARM_FEATURE_NEON) != 0;
if (has_neon) if (has_neon)
CRYPTO_set_NEON_capable(1); CRYPTO_set_NEON_capable(1);
// In all cases, currently, mark the NEON unit as broken because some
// phones can't execute the Poly1305 code correctly. See
// https://code.google.com/p/chromium/issues/detail?id=341598
CRYPTO_set_NEON_functional(0);
#endif #endif
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment