Compile specific parts of the Android build with -O2.

build/android/optimize_speed_template.gypi

Index: build/android/optimize_speed_template.gypi
diff --git a/build/android/optimize_speed_template.gypi b/build/android/optimize_speed_template.gypi
new file mode 100644
index 0000000000000000000000000000000000000000..5c64aa7c223e65a74c607321f871c25569703b38
--- /dev/null
+++ b/build/android/optimize_speed_template.gypi
@@ -0,0 +1,27 @@
+# Copyright (c) 2014 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.
+
+# This file is meant to be included to optimize a target for speed
+# rather than for size on Android.
+# This is used in some carefully tailored targets and is not meant
+# to be included everywhere. If you want to use it for one target,

[pasko, 2014/09/16 11:41:33]

This procedure looks unusual to me. I would prefer reopening "bugs" only if they
were not well fixed originally. I would say:

"""
Before adding the template to another target, please ask in chromium-dev@. See
http://crbug.com/411909
"""

[Fabrice (no longer in Chrome), 2014/09/16 19:17:17]

Done.

+# please reopen the following bug:
+# crbug.com/411909
+
+{
+  'configurations': {
+    'Release': {
+      'target_conditions': [
+        ['_toolset=="target"', {
+          'conditions': [
+            ['OS=="android"', {
+              'cflags!': ['-Os'],
+              'cflags': ['-O2'],

[pasko, 2014/09/16 11:41:33]

stupid idea: can we list all "legitimate" uses of this template in PRESUBMIT?

[Fabrice (no longer in Chrome), 2014/09/16 19:17:17]

I had a quick look but this seems overly complicated.

+            }],
+          ],
+        }],
+      ],
+    },
+  },
+}