diff options
author | primiano <primiano@chromium.org> | 2015-12-04 02:47:03 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-12-04 10:48:00 +0000 |
commit | 79a9c7f80d3059e696b8c8dd0e00546f3fa6edf8 (patch) | |
tree | 21f9d731466dcba802f7345d081a10f9edb002c2 /ui/compositor/compositing_recorder.h | |
parent | e4518f06d1a860c5830ff96817ffe6bf71616e87 (diff) | |
download | chromium_src-79a9c7f80d3059e696b8c8dd0e00546f3fa6edf8.zip chromium_src-79a9c7f80d3059e696b8c8dd0e00546f3fa6edf8.tar.gz chromium_src-79a9c7f80d3059e696b8c8dd0e00546f3fa6edf8.tar.bz2 |
allocator cleanup: set use_allocator=none for mac and ios
Conversely to what the title suggests, this CL doesn't have
any real effect on mac/ios.
Rationale: today mac/ios have use_allocator:tcmalloc just because that
(tcmalloc) is the default value in common.gypi.
As a matter of facts, all the targets that include allocator.gyp
are conditioned by the flags os=win or os=linux (or variants)
and never actually depend on allocator on mac/ios.
In gn instead (see build/config/allocator.gni), use_allocator is
explicitly 'none' for mac and ios.
In essence this CL just re-establishes order in the value of
use_allocator on mac/ios in GYP, setting it to 'none'.
This is part of the allocator cleanup, phase 1
(see http://bit.ly/allocator-cleanup).
After this CL, the various gyp targets are still conditionally
depending on allocator.gyp. Those will be cleaned up in subsequent
CLs.
The effect of this CL can be seen in the diff ninja files:
os=mac: http://pastebin.com/UWvGRUz3
os=mac component=shared_library http://pastebin.com/E8cdSZDe
The only difference there is that the targets 'allocator' and
'allocator_unittest' are not built anymore. Previously they where
built but not depended on.
BUG=564618
Review URL: https://codereview.chromium.org/1497813002
Cr-Commit-Position: refs/heads/master@{#363182}
Diffstat (limited to 'ui/compositor/compositing_recorder.h')
0 files changed, 0 insertions, 0 deletions