Commit d03bd35e authored by thakis@chromium.org's avatar thakis@chromium.org

tcmalloc: Only include cpu profiler in profiling=1 builds.

tcmalloc's cpu profiler code introduces several static initializers, and it's never
used on user machines.  So only include it in profiling=1 builds.
(The comment for profiling% in build/common.gypi even says that this
flag controls if cpuprofiler is used.)

BUG=94925
R=willchan@chromium.org

Review URL: https://codereview.chromium.org/287333002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@271321 0039d316-1c4b-4281-b951-d872f2087c98
parent f8917890
...@@ -367,7 +367,10 @@ ...@@ -367,7 +367,10 @@
# included by allocator_shim.cc # included by allocator_shim.cc
'debugallocation_shim.cc', 'debugallocation_shim.cc',
],
}],
['OS=="win" or profiling!=1', {
'sources!': [
# cpuprofiler # cpuprofiler
'<(tcmalloc_dir)/src/base/thread_lister.c', '<(tcmalloc_dir)/src/base/thread_lister.c',
'<(tcmalloc_dir)/src/base/thread_lister.h', '<(tcmalloc_dir)/src/base/thread_lister.h',
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment