Enable FIXED_POINT and -O3 for Opus when building for ARM

build/common.gypi

 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # IMPORTANT:
 # Please don't directly include this file if you are building via gyp_chromium,
 # since gyp_chromium is automatically forcing its inclusion.
 {
   # Variables expected to be overriden on the GYP command line (-D) or by
   # ~/.gyp/include.gypi.
@@ skipping 3425 matching lines @@
               # (This is currently observed only in chromeos valgrind bots)
               # The following flag is to disable --gc-sections linker
               # option for these bots.
               'no_gc_sections%': 0,
 
               # TODO(bradnelson): reexamine how this is done if we change the
               # expansion of configurations
               'release_valgrind_build%': 0,
             },
             'cflags': [
-              '-O<(release_optimize)',
+              '-O>(release_optimize)',

[tommi (sloooow) - chröme, 2014/06/27 14:27:54]

would it make sense to commit this in a separate CL just to address this
particular issue? (since it doesn't seem specific to the opus change)

[tlegrand1, 2014/06/27 16:37:53]

Yes, I think it does. I'll create a new CL for this change.

On 2014/06/27 14:27:54, tommi wrote:

               # Don't emit the GCC version ident directives, they just end up
               # in the .comment section taking up binary size.
               '-fno-ident',
               # Put data and code in their own sections, so that unused symbols
               # can be removed at link time with --gc-sections.
               '-fdata-sections',
               '-ffunction-sections',
             ],
             'ldflags': [
               # Specifically tell the linker to perform optimizations.
@@ skipping 2090 matching lines @@
     # settings in target dicts.  SYMROOT is a special case, because many other
     # Xcode variables depend on it, including variables such as
     # PROJECT_DERIVED_FILE_DIR.  When a source group corresponding to something
     # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the
     # files to appear (when present) in the UI as actual files and not red
     # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR,
     # and therefore SYMROOT, needs to be set at the project level.
     'SYMROOT': '<(DEPTH)/xcodebuild',
   },
 }