Move the call to CRYPTO_set_NEON_capable up.
BoringSSL needs to probe for NEON support via SIGILL in cases where getauxval isn't provided and the application doesn't do explicit initialisation. However, Chromium might have gone multithreaded by the time that we initialise BoringSSL and, although it doesn't look like we'll race the disposition of SIGILL with anything, it's best not to test that hope. So this change causes CRYPTO_set_NEON_capable to always be called, and to be called before SSL_library_init. BoringSSL will take that as a signal that probing for NEON support isn't needed. BUG=none Review URL: https://codereview.chromium.org/899463002 Cr-Commit-Position: refs/heads/master@{#314201}
Showing
Please register or sign in to comment