Make profiling=1 work for chromium-android

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 2586 matching lines @@
                           '-mtune=xscale',
                           '-msoft-float',
                         ],
                         'defines': [
                           '__ARM_ARCH_5__',
                           '__ARM_ARCH_5T__',
                           '__ARM_ARCH_5E__',
                           '__ARM_ARCH_5TE__',
                         ],
                       }],
+                      ['profiling==1', {
+                        'cflags': [
+                          '-marm', # Probably reduntant, but recommend by "perf" docs.
+                          '-mapcs', # Seems required for -fno-omit-frame-pointer

[digit1, 2012/11/28 22:36:49]

Can I ask you to change this to -mapcs-frame, it is equivalent but slightly less
ambiguous.

Also, do you need to remove -fno-omit-frame-pointer too to ensure that stack
frames are generated for leaf functions?

[Nico, 2012/11/29 00:44:57]

Looks like this didn't happen?

+                        ],
+                      }],
                       ['clang==1', {
                         'cflags!': [
                           # Clang does not support the following options.
                           '-mthumb-interwork',
                           '-finline-limit=64',
                           '-fno-tree-sra',
                           '-fuse-ld=gold',
                           '-Wno-psabi',
                         ],
                       }],
@@ skipping 1261 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',
   },
 }