ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: oxide
     Importance: Medium
     Assignee: Chris Coulson (chrisccoulson)
         Status: In Progress

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
       Status: New => In Progress

** Changed in: oxide
    Milestone: None => branch-1.12

** Changed in: oxide
     Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Summary changed:

- Enable NEON
+ Enable NEON unconditionally

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1517955

Title:
  Enable NEON unconditionally

Status in Oxide:
  In Progress

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1517955/+subscriptions