Perf tests that measure time to load libraries

chrome/chrome_tests.gypi

Index: chrome/chrome_tests.gypi
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi
index 853fbbbea7e9b1ba15a46700e331033fa9884b0e..006c64e499839e975aa4a07c0564b90af13c588a 100644
--- a/chrome/chrome_tests.gypi
+++ b/chrome/chrome_tests.gypi
@@ -2833,6 +2833,24 @@
         '../third_party/webrtc/tools/tools.gyp:rgba_to_i420_converter',
       ],
     },  # target 'webrtc_test_tools'
+    {
+      # Executable to measure time to load libraries.
+      'target_name': 'load_library_perf_tests',

[sky, 2014/03/01 00:09:21]

Is there a reason this needs to be in its own target?

[shadi, 2014/03/01 00:35:22]

Similar to other perf tests targets. Main reason is to be able to run this perf
test on widevine bots for example. There was a discussion with tonyg@ in the
related CL (https://codereview.chromium.org/151283003/) about how we should
combine perf test targets all together... 

+      'type': '<(gtest_target_type)',
+      'dependencies': [
+        '../base/base.gyp:test_support_perf',
+        '../testing/gtest.gyp:gtest',
+        '../testing/perf/perf_test.gyp:*',
+        '../third_party/widevine/cdm/widevine_cdm.gyp:widevine_cdm_version_h',
+      ],
+      'sources': [
+        'browser/load_library_perf_test.cc',
+      ],
+      'include_dirs': [
+        '..',
+        '<(SHARED_INTERMEDIATE_DIR)',
+      ],
+    },  # target 'load_library_perf_tests'
   ],
   'conditions': [
     ['OS=="mac"', {