Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 # Copyright (c) 2012 The Chromium Authors. All rights reserved. | 1 # Copyright (c) 2012 The Chromium Authors. All rights reserved. |
| 2 # Use of this source code is governed by a BSD-style license that can be | 2 # Use of this source code is governed by a BSD-style license that can be |
| 3 # found in the LICENSE file. | 3 # found in the LICENSE file. |
| 4 | 4 |
| 5 # IMPORTANT: | 5 # IMPORTANT: |
| 6 # Please don't directly include this file if you are building via gyp_chromium, | 6 # Please don't directly include this file if you are building via gyp_chromium, |
| 7 # since gyp_chromium is automatically forcing its inclusion. | 7 # since gyp_chromium is automatically forcing its inclusion. |
| 8 { | 8 { |
| 9 # Variables expected to be overriden on the GYP command line (-D) or by | 9 # Variables expected to be overriden on the GYP command line (-D) or by |
| 10 # ~/.gyp/include.gypi. | 10 # ~/.gyp/include.gypi. |
| (...skipping 420 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 431 'tsan_blacklist%': '<(PRODUCT_DIR)/../../tools/memory/tsan_v2/ignores.txt' , | 431 'tsan_blacklist%': '<(PRODUCT_DIR)/../../tools/memory/tsan_v2/ignores.txt' , |
| 432 | 432 |
| 433 # Enable building with MSan (Clang's -fsanitize=memory option). | 433 # Enable building with MSan (Clang's -fsanitize=memory option). |
| 434 # MemorySanitizer only works with clang, but msan=1 implies clang=1 | 434 # MemorySanitizer only works with clang, but msan=1 implies clang=1 |
| 435 # See http://clang.llvm.org/docs/MemorySanitizer.html | 435 # See http://clang.llvm.org/docs/MemorySanitizer.html |
| 436 'msan%': 0, | 436 'msan%': 0, |
| 437 'msan_blacklist%': '<(PRODUCT_DIR)/../../tools/msan/blacklist.txt', | 437 'msan_blacklist%': '<(PRODUCT_DIR)/../../tools/msan/blacklist.txt', |
| 438 # Track where uninitialized memory originates from. From fastest to | 438 # Track where uninitialized memory originates from. From fastest to |
| 439 # slowest: 0 - no tracking, 1 - track only the initial allocation site, 2 | 439 # slowest: 0 - no tracking, 1 - track only the initial allocation site, 2 |
| 440 # - track the chain of stores leading from allocation site to use site. | 440 # - track the chain of stores leading from allocation site to use site. |
| 441 'msan_track_origins%': 1, | 441 'msan_track_origins%': 2, |
|
Nico
2015/03/19 18:31:00
unrelated?
earthdok
2015/03/23 13:02:56
There haven't been any builders using msan_track_o
earthdok
2015/03/23 13:06:56
I'll do it in a separate CL.
| |
| 442 | 442 |
| 443 # Enable building with UBSan (Clang's -fsanitize=undefined option). | 443 # Enable building with UBSan (Clang's -fsanitize=undefined option). |
| 444 # -fsanitize=undefined only works with clang, but ubsan=1 implies clang=1 | 444 # -fsanitize=undefined only works with clang, but ubsan=1 implies clang=1 |
| 445 # See http://clang.llvm.org/docs/UsersManual.html | 445 # See http://clang.llvm.org/docs/UsersManual.html |
| 446 'ubsan%': 0, | 446 'ubsan%': 0, |
| 447 'ubsan_blacklist%': '<(PRODUCT_DIR)/../../tools/ubsan/blacklist.txt', | 447 'ubsan_blacklist%': '<(PRODUCT_DIR)/../../tools/ubsan/blacklist.txt', |
| 448 | 448 |
| 449 # Enable building with UBsan's vptr (Clang's -fsanitize=vptr option). | 449 # Enable building with UBsan's vptr (Clang's -fsanitize=vptr option). |
| 450 # -fsanitize=vptr only works with clang, but ubsan_vptr=1 implies clang=1 | 450 # -fsanitize=vptr only works with clang, but ubsan_vptr=1 implies clang=1 |
| 451 'ubsan_vptr%': 0, | 451 'ubsan_vptr%': 0, |
| (...skipping 5571 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 6023 # settings in target dicts. SYMROOT is a special case, because many other | 6023 # settings in target dicts. SYMROOT is a special case, because many other |
| 6024 # Xcode variables depend on it, including variables such as | 6024 # Xcode variables depend on it, including variables such as |
| 6025 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something | 6025 # PROJECT_DERIVED_FILE_DIR. When a source group corresponding to something |
| 6026 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the | 6026 # like PROJECT_DERIVED_FILE_DIR is added to a project, in order for the |
| 6027 # files to appear (when present) in the UI as actual files and not red | 6027 # files to appear (when present) in the UI as actual files and not red |
| 6028 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR, | 6028 # red "missing file" proxies, the correct path to PROJECT_DERIVED_FILE_DIR, |
| 6029 # and therefore SYMROOT, needs to be set at the project level. | 6029 # and therefore SYMROOT, needs to be set at the project level. |
| 6030 'SYMROOT': '<(DEPTH)/xcodebuild', | 6030 'SYMROOT': '<(DEPTH)/xcodebuild', |
| 6031 }, | 6031 }, |
| 6032 } | 6032 } |
| OLD | NEW |