Revert "Disable all NEON in BoringSSL if has_broken_neon is set."

Revert "Disable all NEON in BoringSSL if has_broken_neon is set."

This reverts commit 396d38c7d55e1c039069017afd74488cac9060cd.

The change caused the has_broken_neon to regress because, at the corresponding
BoringSSL revision, the getauxval logic would run afterwards and clear the
setting.

For M50, revert this change to restore the old behavior. Conveniently, the
BoringSSL half of this pair (85003903fc58d8825e02162fd33a9b9c28fdec35) rolled
into Chromium after the branch point and was later subsumed by moving the check
into BoringSSL itself, so trunk and M51 have the correct broken_neon/getauxval
interaction. (Though they still regressed the check due to an interation with
Chromium setting arm_neon=1. This has since been fixed.)

BUG=606629
TBR=agl@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/a4ab48f3dac253ee97295ad2fb17a9fd6cda15ea

[davidben, 2016-05-02 21:28:15]

Description was changed from

==========
Revert "Disable all NEON in BoringSSL if has_broken_neon is set."

This reverts commit 396d38c7d55e1c039069017afd74488cac9060cd.

The change caused the has_broken_neon to regress because, at the corresponding
BoringSSL revision, the getauxval logic would run afterwards and clear the
setting.

For M50, revert this change to restore the old behavior. Conveniently, the
BoringSSL half of this pair (85003903fc58d8825e02162fd33a9b9c28fdec35) rolled
into Chromium after the branch point and was later subsumed by moving the check
into BoringSSL itself, so trunk and M51 have the correct broken_neon/getauxval
interaction. (Though they still regressed the check due to an interation with
Chromium setting arm_neon=1. This has since been fixed.)

BUG=606629
TBR=agl@chromium.org
==========

to

==========
Revert "Disable all NEON in BoringSSL if has_broken_neon is set."

This reverts commit 396d38c7d55e1c039069017afd74488cac9060cd.

The change caused the has_broken_neon to regress because, at the corresponding
BoringSSL revision, the getauxval logic would run afterwards and clear the
setting.

For M50, revert this change to restore the old behavior. Conveniently, the
BoringSSL half of this pair (85003903fc58d8825e02162fd33a9b9c28fdec35) rolled
into Chromium after the branch point and was later subsumed by moving the check
into BoringSSL itself, so trunk and M51 have the correct broken_neon/getauxval
interaction. (Though they still regressed the check due to an interation with
Chromium setting arm_neon=1. This has since been fixed.)

BUG=606629
TBR=agl@chromium.org

Committed:
https://chromium.googlesource.com/chromium/src/+/a4ab48f3dac253ee97295ad2fb17...
==========

[davidben, 2016-05-02 21:28:17]

Committed patchset #1 (id:1) manually as
a4ab48f3dac253ee97295ad2fb17a9fd6cda15ea (presubmit successful).

[agl, 2016-05-02 21:37:46]

lgtm