Enable NEON unconditionally

Bug #1517955 reported by Chris Coulson on 2015-11-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Medium
Chris Coulson

Bug Description

We currently build with arm_neon=0, arm_neon_optional=1 which turns on the NEON run-time detection. However, whilst this is the configuration for Chrome/Android it's broken in various parts of Chromium/Linux:

- webrtc only contains runtime detection for Android
- Runtime detection in openmax also depends on Android.

The arm_neon=0,arm_neon_optional=0 build is also broken (and is completely untested).

Google are removing support for this configuration, making neon mandatory in Chromium (see https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/niJlCmipYAQ). We should just make this change in Oxide now, which allows us to stop modifying webrtc and openmax.

Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
importance: Undecided → Medium
milestone: none → branch-1.12
status: New → In Progress
summary: - Enable NEON
+ Enable NEON unconditionally
Changed in oxide:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers