aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDan Albert <danalbert@google.com>2019-09-04 13:15:15 -0700
committerDan Albert <danalbert@google.com>2019-09-04 14:23:53 -0700
commita78a3dc9ed516d5057a2043c72c5563465c2dca0 (patch)
tree66950861438ccb53149ce4bac6bdd01b3dab5479 /docs
parentd0bb5bc2b9e4592cf09a6c4a2231194fe51b5315 (diff)
downloadndk-a78a3dc9ed516d5057a2043c72c5563465c2dca0.tar.gz
Fix build system maintainers guide wrt neon.
Test: None Bug: https://github.com/android-ndk/ndk/issues/859 Change-Id: Ib91a7eca6737020e4b379e7ffa6e76e2afec1525
Diffstat (limited to 'docs')
-rw-r--r--docs/BuildSystemMaintainers.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/BuildSystemMaintainers.md b/docs/BuildSystemMaintainers.md
index 4aced904c..16ec28d3f 100644
--- a/docs/BuildSystemMaintainers.md
+++ b/docs/BuildSystemMaintainers.md
@@ -89,15 +89,16 @@ devices and nearly all 32-bit ARM devices running at least Android Marshmallow
is possible that extant devices that were upgraded to Marshmallow do not include
NEON support.
-Enabling NEON can significantly improve application performance.
+NEON can significantly improve application performance.
-To enable NEON, pass `-mfpu=neon` when compiling.
-
-Note: Clang automatically enables NEON for API levels 23 (Marshmallow) and
-higher.
+Clang automatically enables NEON for all API levels. ARM devices without NEON
+are uncommon. To support non-NEON devices, pass `-mfpu=vfpv3-d16` when
+compiling. Alternatively, use the Play Console to [blacklist CPUs] without NEON
+to disallow your app from being installed on those devices.
[Android CDD]: https://source.android.com/compatibility/cdd
[NEON]: https://developer.arm.com/technologies/neon
+[blacklist CPUs]: https://support.google.com/googleplay/android-developer/answer/7353455?hl=en
### OS Versions
[OS Versions]: #os-versions